Swift 6

Cross‑Platform Ambitions and Role in the Stack

• Many see Swift 6 as a major step for cross‑platform, “batteries included” development, especially due to a more complete, cross‑platform Foundation and static Linux SDK.
• Apple is perceived as aiming to use Swift up and down the stack (apps, system code, firmware, drivers) and as a long‑term C++ successor within its ecosystem, but not necessarily to “replace every language.”
• Some doubt Swift’s suitability for bare‑metal / very low‑level work, calling it verbose and unnatural there. Others report Apple is already using it in embedded processors and secure enclave‑like contexts.

Ecosystem, Platforms, and Web/Server Use

• SwiftPM works on Linux; main blocker is limited, well‑tested cross‑platform libraries, especially on Windows.
• Swift on the server exists (e.g., Vapor, Swift‑NIO) and is considered fine for simple services, but not mainstream. Docker‑based Linux builds are often slow and tooling is weaker than typical Linux web stacks.
• Lack of Android‑first support and official cross‑platform tooling is seen as a barrier to Swift becoming “mainstream” vs Kotlin, C#, Dart/Flutter, etc.

Performance: Compile Time, Type Checking, Runtime

• Frequent complaints about slow compilation, especially for SwiftUI and macro‑heavy code; type‑checker timeouts on complex expressions remain a major pain point.
• Some argue Swift is often slower than Objective‑C and lags C/C++/Rust, others counter that benchmarks show Swift far ahead of Python/JavaScript and within a small factor of C for many tasks.
• ARC vs tracing GC is hotly debated; ARC is called both a strength (no stop‑the‑world pauses, good for constrained devices) and a throughput disadvantage.

Concurrency, Ownership, and Safety

• Swift 6’s data‑race safety, ownership features, and C++ interop are widely praised conceptually, with comparisons to a “friendlier Rust.”
• In large legacy codebases, enabling full Swift 6 concurrency checking can require major rewrites, leading some to consider other languages instead. Incremental migration support is appreciated.
• New ownership syntax (~Copyable, consuming) is seen as powerful but initially confusing and syntactically dense.

Language Complexity, Governance, and Tooling

• Multiple commenters say Swift is becoming “C++‑like” in complexity with too much syntax and “magic” (result builders, macros, SwiftUI patterns).
• SwiftUI is described as elegant in theory but buggy, slow to compile, and with poor error messages; some feel it harms Swift’s reputation.
• Xcode and Apple tooling are repeatedly criticized as unstable, slow, and far behind top IDEs; this, plus Apple‑driven design decisions and hard‑coded compiler exceptions, fuels concern about governance and long‑term maintainability.