Swift 6.4 is now available, and its headline change is structural: Swift Build is now the default in Swift Package Manager, so projects build the same way on Linux, macOS, and Windows. The release, authored by Joe Heck and Holly Borla and published on Swift.org on September 15, positions the language as a choice "across the stack, from apps and servers to systems code, embedded devices, and the browser." ## One Build System Everywhere The Swift Package Manager, created by Apple in 2015 as a command-line automation and dependency management tool, now uses Swift Build as its default build platform. The Register's coverage notes that Swift Build itself is a collection of interoperable software development components, and its promotion to default means a SwiftPM project produces consistent builds across all three major desktop platforms. SwiftPM 6.4 also adds Software Bill of Materials generation under SE-0509, supporting SBOM documents in either SPDX or CycloneDX format — a supply-chain security capability increasingly demanded by enterprise buyers and regulators. The unified build extends to Android too: Swift Build now supports Android in SwiftPM, removing the need for a post-install script, and the Swift SDK for Android is built with the new LTS NDK 30. ## Subprocess Reaches 1.0 The Subprocess library, introduced as an initial 0.1 version in 2025, has reached 1.0. It provides a stable, cross-platform package to run and interact with subprocesses, built from the ground up using Swift concurrency. Interoperability reaches further this release as well. Swift's Span now bridges directly with C++20's std::span, letting developers pass a Span to a C++ API that expects a std::span and receive one back without manual conversion code. The Swift/Java interop project extends its support for calling async and throwing functions to protocol and callback wrappers, adds automatic Runnable mapping for closures, and supports Java record types. ## The Browser and the Microcontroller Swift runs faster in the browser with WebAssembly bridging through JavaScriptKit up to 40 times faster than earlier dynamic bridging, and the Wasm SDK is now available directly from Swift.org, so compiling Swift for the browser requires no extra setup beyond adding the SDK. Embedded Swift grows more capable with support for existential types, letting developers naturally express heterogeneous collections on microcontroller-class targets, and richer error handling for firmware code. Performance improves while maintaining memory safety: new array types hold non-copyable elements without copy-on-write overhead, the Iterable protocol iterates without copies, and UniqueBox provides a smart pointer that uniquely owns a heap value without reference counting. ## Everyday Code Gets Simpler The release also streamlines day-to-day programming. Optional some and any types no longer require parentheses, so instead of wrapping a type like (some Rocket)?, developers can write some Rocket? directly under SE-0521. Source-level control over compiler warnings arrives through the new @diagnose attribute under SE-0522, letting teams suppress warnings or promote them to errors directly in code. Module selectors under SE-0491 clarify which API to use when multiple libraries conflict, and developers can now call async functions in a defer block under SE-0493, with the withTaskCancellationShield API under SE-0504 ensuring necessary cleanup work is not cancelled. Tooling gains include more robust debugging — LLDB now imports modules through precise dependency tracking, shrinking debug builds on Linux and Windows significantly — and broader IDE support, with the VS Code extension now available on the Open VSX Registry so it works in Cursor, Antigravity, Kiro and other development tools. Swift Testing migration also gets easier: developers can now safely use XCTAssert in Swift Testing tests or #expect within XCTests, and the swift test command can repeat test cases to focus debugging time. For a language once seen as Apple-exclusive, Swift 6.4 reads less like a point release and more like a platform declaration: same builds everywhere, from datacentre to microcontroller to browser tab. ## Why the Build Unification Matters Build-system fragmentation has been one of the quiet friction points of cross-platform Swift development. Teams targeting Linux servers and Windows machines alongside Apple hardware previously navigated differing build behaviours, and the Swift Build promotion collapses that variance into a single pipeline. For continuous-integration setups, the practical effect is simpler: one build definition, three operating systems, no platform-specific branches to maintain. The SBOM generation addition answers a different pressure. Software supply-chain security mandates in the United States and Europe increasingly require machine-readable inventories of dependencies, and SPDX and CycloneDX are the two formats public procurement rules recognise. Shipping that natively in SwiftPM means Swift projects can satisfy the requirement without bolting on third-party tooling. ## A Language Widening Its Footprint The release pattern across recent Swift versions shows a deliberate strategy: each iteration extends the language further from its Apple origin story. This one touches servers through Subprocess 1.0, systems code through C++ and Java interop, browsers through a 40-times-faster WebAssembly bridge, and hardware through Embedded Swift existential types. None of the platform work displaces Apple platforms, which still benefit from first-party tooling. But the trajectory is legible: Swift is being positioned wherever Swift developers might want to take it, with the build system unification removing one of the last structural reasons a team would keep Swift code siloed on Apple operating systems. For developers, the migration path is deliberately gentle. The release notes describe the same package building identically once SwiftPM updates, with no required changes to package manifests. The harder work, in interop boundaries and embedded targets, is opt-in — a pattern the project has maintained as it courts audiences well beyond the App Store.