# Swift.org Swift is a general-purpose programming language built using a modern approach to safety, performance, and software design patterns. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Swift 6.4 Released DevFeed: [Swift 6.4 Released]() Original publisher: [Read original article]() Author: Holly Borla Published: 2026-09-15T07:30:00Z Content type: release Language: en Sources: [Swift.org]() Topics: [Swift](), [cross-platform](), [Programming](), [Memory Safety](), [WebAssembly](), [browser](), [Microcontroller]() Tags: [cross-platform](), [errors](), [libraries](), [linux](), [macos](), [memory-safety](), [programming](), [swift](), [webassembly]() ### AI overview Swift 6.4 is now available with Swift Build as the default in Swift Package Manager, a stable cross-platform Subprocess API, expanded C++20 and Java interoperability, faster WebAssembly support, broader embedded Swift capabilities, and performance improvements that maintain memory safety. ### Source excerpt Swift 6.4 is now available. Swift aims to be a great choice across the stack, from apps and servers to systems code, embedded devices, and the browser. This release deepens that support, and makes everyday code easier to write. Highlights include: Swift Build is now the default in Swift Package Manager, so your projects build the same way on Linux, macOS, and Windows. Subprocess reaches 1.0, a stable, cross-platform way to run and interact with other programs from Swift, from command-line tools to streaming processes. Interoperability reaches further, with Swift's Span now bridging directly with C++20's std::span, and Swift/Java interop extending its async and callback support. Swift runs faster in the browser, with WebAssembly bridging through JavaScriptKit up to 40 times faster, and the Wasm SDK available directly from Swift.org. Embedded Swift grows more capable, with support for existential types and richer error handling for microcontroller-class targets. Performance improves while maintaining memory safety, with new array types that hold non-copyable elements without copy-on-write overhead, and the new Iterable protocol for iterating without copies. There's so much more. Read on for a detailed guide to the new changes, or see the Swift Evolution dashboard for the full list of proposals in Swift 6.4. Simpler and clearer code Swift 6.4 streamlines your day-to-day programming to make your code simpler and clearer. More natural optional some and any types. When writing an optional some or any type, you no longer have to wrap the type in parentheses. Instead of (some Rocket)?, you can simply write some Rocket? (SE-0521). Source-level control over compiler warnings. When you need to control the behavior of warnings in your project, such as suppressing warnings or promoting them to errors, you can now define the warning behavior directly in your code using the new @diagnose attribute (SE-0522). Clarify which API to use when multiple libraries conflict. When multiple ## Module Tracking in Swift Debug Info DevFeed: [Module Tracking in Swift Debug Info]() Original publisher: [Read original article]() Author: Adrian Prantl Published: 2026-09-11T15:30:00Z Content type: tutorial Language: en Sources: [Swift.org]() Topics: [debugging](), [debug](), [toolchain](), [C++]() Tags: [cmake](), [debug](), [debugger](), [debugging](), [jit](), [swift]() ### AI overview Swift 6.3 and the upcoming Swift 6.4 improve how explicitly built Swift modules are referenced in debug information. The article explains how this helps LLDB locate modules for expression evaluation, improving debugging reliability and reducing build products, while noting that custom build systems may need adjustments. ### Source excerpt When your Swift program hits a breakpoint and stops so you can inspect it, the debugger's expression evaluator has to find the exact Swift module your code was built from. Until now, that lookup wasn't always precise. The upcoming Swift 6.4 release will include changes, begun in Swift 6.3, that address this by updating how the Swift compiler references explicitly-built Swift modules in debug info. The majority of developers will automatically benefit from faster, more reliable debugging and smaller build products, without any modifications to their SwiftPM or Xcode projects. For developers who maintain their own build systems using, for example, Bazel, Buck, or CMake, some adjustments may be necessary to take advantage of these changes. This article explains how the debugger uses Swift modules. Next, it describes how Swift 6.3 changes the way modules are tracked in debug info to solve several problems with the previous representation. Finally, it shows how to adjust build systems to take advantage of the new representation and eliminate some build steps that are no longer necessary. Swift modules and expression evaluation LLDB's standout feature is its powerful expression evaluator. Because LLDB embeds the Clang and Swift compilers, it can JIT-compile any valid source code and run it in the context of your application while stopped at a breakpoint. This includes not just calling code in your application, but also defining new data types, functions, and closures. Debugging features that are usually reserved for interpreted or JIT-compiled languages like JavaScript become available to ahead-of-time-compiled languages like C++ and, of course, Swift! In order to JIT-compile user expressions that make use of data types defined in the debugged program, LLDB's embedded Swift compiler needs to import the Swift modules defining those types. In a world before explicitly-built modules, LLDB would find the base name of the main module at the current breakpoint in the debug info ## What's new in Swift: August 2026 Edition DevFeed: [What's new in Swift: August 2026 Edition]() Original publisher: [Read original article]() Author: Dave Lester Published: 2026-09-04T16:30:00Z Content type: news Language: en Sources: [Swift.org]() Topics: [modern web development](), [Vapor](), [Back end]() Tags: [backend](), [cloudflare](), [demo](), [frontend](), [swift](), [wasm](), [webassembly]() ### AI overview A Swift community update highlights Elementary and ElementaryUI, projects for server-rendered and browser-based web UIs. It also describes Swift-to-WebAssembly progress and a Cloudflare full-stack demo using shared message types. ### Source excerpt Welcome to "What's new in Swift," a curated digest of releases, videos, and discussions in the Swift project and community. Here's an update from guest contributor Simon Leeb on Swift's progress as a language for web scenarios: Hi, Simon here! I am the creator of the elementary-swift project, a collection of packages born from a simple wish: I want to build web UIs in Swift and ultimately help Swift become a first-class choice for the web. This journey began after I started using Swift for backend services. The web frontend, however, still lived in a separate ecosystem, and I really wanted it to feel as ergonomic, safe, and efficient as the Swift I was writing everywhere else. That led to the creation of Elementary: a modern and efficient HTML rendering library with a familiar declarative API, built for the web. It integrates easily with frameworks like Vapor and Hummingbird, and has become a practical option for server-rendered web UIs. Around that same time, years of community work in the swift-wasm project made compiling Swift to WebAssembly increasingly viable, while Embedded Swift was taking its first experimental steps. This made me wonder: "How hard can it be to use Embedded Swift and build a state-driven web UI framework that produces tiny WebAssembly binaries?" Turns out: quite hard, actually! But it was too late. Despite my better judgment, I was in the middle of creating what is now known as ElementaryUI. Where Elementary renders HTML on the server, ElementaryUI runs in the browser itself. You can watch my talk at Swift@FOSDEM 2026 if you want to know more about the why, what, and how. To showcase where the project is heading, I recently posted a small Full-Stack Swift on Cloudflare demo. It features Swift in the browser communicating with a Swift backend on an edge worker through shared message types. I hope it gives people a concrete sense of how much the core technologies and the surrounding tooling have advanced. ElementaryUI is still young, with plen ## Embedded Swift Improvements Coming in Swift 6.4 DevFeed: [Embedded Swift Improvements Coming in Swift 6.4]() Original publisher: [Read original article]() Author: Doug Gregor Published: 2026-08-20T13:45:00Z Content type: article Language: en Sources: [Swift.org]() Topics: [Swift](), [Code]() Tags: [code](), [development](), [embedded](), [features](), [performance](), [post](), [release](), [swift]() ### AI overview This article describes improvements coming to Embedded Swift in Swift 6.4, including broader language compatibility, generalized existential type support, and untyped throws. It also discusses the effects of dynamic features on runtime performance and code size. ### Source excerpt Embedded Swift is a subset of Swift that's designed for low resource usage, making it capable of running on constrained environments like microcontrollers. Using a special compilation mode, Embedded Swift produces significantly smaller binaries than regular Swift. While a subset of the full language, the vast majority of the Swift language works exactly the same in Embedded Swift. Additional information is described in the Embedded Swift vision document. Embedded Swift is evolving rapidly. Following our updates on Embedded Swift improvements in Swift 6.3 late last year, this post describes a number of additional improvements made in the upcoming Swift 6.4 release. You can try them out today with a Swift development snapshot. Language improvements Embedded Swift continues to expand its subset of the language to include more aspects of "full" Swift, making it easier than ever to bring compatibility with Embedded Swift to existing Swift code bases. Many of these features have some dynamic aspect to them, meaning that they have an impact on runtime performance (for example, due to indirect calls) and code size (due to requiring additional metadata). However, this impact only occurs where these dynamic language features are actually used: code that is highly sensitive to code size and performance can choose to avoid them, for example by enabling warnings in the PerformanceHints diagnostic group. Generalized support for existential (any) types any) types section" href="#generalized-support-for-existential-any-types"> Embedded Swift previously only supported existential (any) types that had an AnyObject constraint, meaning they could only be used with class instances. Now, all any types are available in Embedded Swift, including Any itself. For example: protocol P { func method() } extension Int: P { func method() { print("\(self) is here") } } let a: any P = 17 a.method() // prints "17 is here" The Embedded Swift generics compilation model, which requires that all generic ## What's new in Swift: July 2026 Edition DevFeed: [What's new in Swift: July 2026 Edition]() Original publisher: [Read original article]() Author: Dave Lester Published: 2026-08-07T15:30:00Z Content type: news Language: en Sources: [Swift.org]() Topics: [releases]() Tags: [community](), [contributors](), [open-source](), [pull-requests](), [releases](), [swift](), [systems]() ### AI overview A Swift community digest covering releases, discussions, and ways to contribute beyond language and compiler work. It also highlights ongoing systems-programming work on ownership and lifetime features. ### Source excerpt Welcome to "What's new in Swift," a curated digest of releases, videos, and discussions in the Swift project and community. Swift is built by contributors working on far more than the language and compiler. Alexander Sandberg reflects on what that kind of contribution looks like, and why there's a place for you too: Hi, I'm Alex. Four years ago I joined the Swift Website Workgroup to help care for the website you're reading this on. I was still fairly new to the Swift community then, but I wanted to get involved somehow and make a difference. Contributing to Swift sounds like it should involve working on the compiler or writing and reviewing language evolution proposals, but there's a lot going on around the language itself too. What I actually spent my time doing was helping improve the site's content and navigation, taking part in the big redesign, writing release blog posts, reviewing pull requests, and answering issues and forum posts. All of it is work anyone can learn to do, and all of it ends up in front of everyone who comes to Swift.org--which made even the smallest fixes feel worth doing. The Website Workgroup happened to be my way in, but there are groups like it across the project--server, testing, Windows, Android, and more--each a handful of people looking after their part of the ecosystem. Whatever you're good at or curious about, there's probably a corner of Swift that could use your help. The community page is a good place to start looking, and the people you'll meet are some of the friendliest I've come across in open source. After four years, I've stepped away to focus on other things in life. Thank you to everyone I got to work with over these years! I'm leaving the workgroup, but not the community, and I'll still be around helping push Swift forward where I can. For more information about workgroups, the How we work page lists all workgroups. And on the Swift forums you'll often see workgroups sharing open meetings if you're looking to get involved ## What's new in Swift: June 2026 Edition DevFeed: [What's new in Swift: June 2026 Edition]() Original publisher: [Read original article]() Author: Dave Lester Published: 2026-07-02T16:00:00Z Content type: news Language: en Sources: [Swift.org]() Topics: [Swift](), [releases](), [networking](), [Operating system](), [cross-platform](), [foundation-models](), [LLMs]() Tags: [2026](), [announcements](), [apple](), [cross-platform](), [developers](), [event](), [linux](), [llms](), [networking](), [releases](), [swift](), [wwdc]() ### AI overview This June 2026 digest covers Swift project and community news, including WWDC announcements. It highlights Swift adoption in parts of Apple's operating system kernel, upcoming Swift 6.4 features, a Swift rewrite of Apple's QUIC transport layer made available for cross-platform use through SwiftNIO, and Foundation Models framework utilities for working with LLMs on Apple platforms and selected Linux distributions. ### Source excerpt Welcome to "What's new in Swift," a curated digest of releases, videos, and discussions in the Swift project and community. June was an exciting month for Swift, featuring announcements at WWDC and community events around the globe. We invited the organizers of one of them to share with us: Hey, it's Mikaela and Adrian. We are organizers of CommunityKit, a community-organized conference that takes place the same week as WWDC, and iOSDevHappyHour, a monthly online meetup that keeps the community connected year-round. This is our fifth year coming out to Cupertino, and we love being able to create a place for the community to thrive, no matter where developers live. CommunityKit brought together over 250 developers in real life to geek out over the announcements, stay for the community and vibes, see what everyone is creating, and learn from each other. Some of the highlights from this year's event were the Indie Fair, where developers showcased their apps; the Watch Party, our annual gathering to watch the keynotes together; and Make Something, Ship Nothing, a hands-on postcard-making hangout to close the week. This year we also introduced workshops, including "Inclusive by Design" by Danielle Lewis, and for the Swift community: "Write Faster, Smarter Swift" by Paul Hudson. We can't wait to hear about what everyone builds and brings to next year's Indie Fair, and hope to see you at CommunityKit and iOSDevHappyHour! Now on to other news about Swift: WWDC26 highlights At its WWDC26 conference, Apple provided an update on its adoption of Swift and made a variety of new Swift-related announcements. Some highlights: During the Platforms State of the Union, Apple announced that parts of the core operating system kernel are being written in Swift for upcoming releases. What's new in Swift featured changes in Swift since last year, including a preview of what's coming in Swift 6.4, like up to 4x faster URL parsing and support for async code in defer blocks. The QUIC transpor ## Swift Package Index Update DevFeed: [Swift Package Index Update]() Original publisher: [Read original article]() Author: Dave Lester Published: 2026-06-23T14:00:00Z Content type: news Language: en Sources: [Swift.org]() Topics: [Swift](), [Linux](), [Android](), [WebAssembly]() Tags: [android](), [announcement](), [ecosystem](), [linux](), [swift](), [update](), [webassembly]() ### AI overview Swift Package Index has joined Apple while continuing to support package discovery, documentation, dependency evaluation, and compatibility testing across Swift's expanding multi-platform ecosystem, including Linux, Android, and WebAssembly. ### Source excerpt Since its launch, Swift Package Index has become an essential part of the Swift ecosystem, helping developers discover quality packages, evaluate compatibility, and make informed decisions about dependencies. Started by Dave Verwer and Sven A. Schmidt, the project currently indexes thousands of packages and serves as a central hub for package documentation. Recently, Swift Package Index has grown alongside the Swift project's multi-platform expansion, extending its compatibility testing to encompass Linux, Android, and WebAssembly. Today, Swift Package Index announced that it has joined Apple and continues its mission: Together, we're building a comprehensive package registry to serve the Swift community's evolving needs. Learn more by reading the Swift Package Index announcement. ## Swift at Apple: Migrating the TrueType Hinting Interpreter DevFeed: [Swift at Apple: Migrating the TrueType Hinting Interpreter]() Original publisher: [Read original article]() Author: Scott Perry Published: 2026-06-12T10:00:00Z Content type: article Language: en Sources: [Swift.org]() Topics: [Swift](), [Font](), [Memory Safety](), [Security](), [Memory safety verification](), [Web](), [pdf]() Tags: [apple](), [applications](), [code](), [fonts](), [memory-safety](), [performance](), [security](), [swift](), [web]() ### AI overview Apple describes rewriting its TrueType hinting interpreter from C to memory-safe Swift for Fall 2025 releases. The rewrite addresses the security risks of processing untrusted fonts and reportedly improves performance by 13% on average. ### Source excerpt TrueType is a widely used vector font standard for rendering text in web pages, PDFs, operating systems, and applications. Familiar fonts like Helvetica, Garamond, and Monaco are all built on TrueType outlines. The format specifies a hinting interpreter intended to help outlines rasterize faithfully on low-resolution displays. Modern high-resolution displays enable beautiful typography from outlines alone, but TrueType fonts that need hinting to render legibly remain in use and we continue to support them. Font parsers process data from untrusted sources, making the TrueType hinting interpreter a security-critical attack surface. To make the format more resilient on Apple platforms, we rewrote its hinting interpreter from C to memory-safe Swift for the Fall 2025 releases. In addition to memory safety, we also improved performance: on average, our Swift interpreter runs 13% faster than the C interpreter it replaced. To accompany this post, we've also published the source code of the Swift TrueType hinting interpreter. We hope sharing our experience helps others doing similar work in Swift. TrueType and the hinting engine Apple developed TrueType in the late 1980s and released it with the launch of System 7 in 1991. TrueType was a major breakthrough for the time: it gave font developers enormous control over how glyphs are displayed, with an advanced grid-fitting algorithm and a sophisticated hinting engine built around a special-purpose bytecode interpreter. TrueType did all this on computers that were vastly less powerful than today's, so it had to be extremely well-tuned for performance. Then the internet revolutionized how fonts were used. TrueType became embeddable in PDF files in 1994 and in web pages in 2008, and it remains as relevant as ever. However, these new use cases brought additional risk: TrueType could now be exposed to untrusted fonts from anywhere on the internet. TrueType fonts may contain programs the hinting engine runs through a bytecode interpr ## Announcing the Networking Workgroup DevFeed: [Announcing the Networking Workgroup]() Original publisher: [Read original article]() Author: Franz Busch Published: 2026-06-04T10:00:00Z Content type: news Language: en Sources: [Swift.org]() Topics: [networking](), [Swift](), [API](), [Protocol (disambiguation)](), [client](), [Concurrency](), [TLS (Transport Layer Security)](), [servers](), [WebSocket]() Tags: [announcement](), [api](), [architecture](), [concurrency](), [http](), [networking](), [responses](), [server](), [swift](), [tls]() ### AI overview Swift has announced a community-led Networking workgroup to guide the evolution of networking libraries, protocols, and APIs. Its goals include a unified, layered networking stack, interoperable networking types, modern HTTP client and server APIs built on structured concurrency, and shared implementations of protocols such as TLS, HTTP versions, QUIC, and WebSockets. ### Source excerpt The Swift Ecosystem Steering Group is excited to announce the creation of the Networking workgroup! Workgroups are community-led efforts, formally recognized by the project, to advance key areas of Swift. The primary goal is to guide the evolution of networking libraries, protocols, and APIs in the Swift ecosystem, making networking in Swift excellent everywhere: high-level and safe by default, modular and interoperable, cross-platform, and observable. Networking is one of the most common entry points for Swift developers, and the ecosystem has matured significantly over the years. Foundational libraries like SwiftNIO, AsyncHTTPClient, and swift-http-types, alongside platform stacks such as URLSession and Network.framework, power networking across apps, servers, and beyond. The workgroup will build upon these efforts and pursue the long-term directions outlined in the Networking vision, focusing on work to: Define a unified networking stack with a coherent layered architecture, from shared I/O primitives at the foundation, through common protocol implementations, to ergonomic client and server APIs at the top. Define currency types that let libraries interoperate without coupling to specific implementations, such as IP addresses, hostnames, ports, and HTTP requests and responses. Evolve HTTP APIs by designing and guiding a modern, unified HTTP client and server API built on structured concurrency. Guide the evolution of shared protocol implementations (TLS, HTTP/1.1, HTTP/2, HTTP/3, QUIC, WebSockets) so improvements benefit the entire ecosystem rather than being duplicated across libraries. The new Networking workgroup joins a growing list of Swift workgroups, including the Android workgroup, Windows workgroup, and Build and Packaging workgroup, which were all added in the past year. To learn more and get involved: Discuss this announcement on the forums, and share ideas in the Networking category. Learn more about the Networking workgroup by reading its charter. Th ## What's new in Swift: May 2026 Edition DevFeed: [What's new in Swift: May 2026 Edition]() Original publisher: [Read original article]() Author: Dave Lester Published: 2026-06-03T21:45:00Z Content type: article Language: en Sources: [Swift.org]() Topics: [Swift](), [SDKs](), [Back end](), [iOS](), [MLX](), [wasm](), [WebAssembly](), [AWS Lambda]() Tags: [aws](), [aws-lambda](), [backend](), [community](), [conferences](), [ios](), [local](), [mlx](), [news](), [releases](), [serverless](), [swift](), [wasm](), [webassembly]() ### AI overview A curated May 2026 digest of Swift community activity, including meetup videos, backend development resources, the Temporal Swift SDK, AWS Lambda, MLX for iOS, and Swift for WebAssembly updates. ### Source excerpt Welcome to "What's new in Swift," a curated digest of releases, videos, and discussions in the Swift project and community. To start, we're focusing on some of the many local meetup groups sharing Swift content: Around the world, local meetup groups and conferences bring Swift developers together, and some even predate Swift itself! Many have YouTube channels where they share videos from their events, so you can tune in remotely. Let's highlight a few. In May the SF Swift meetup hosted a talk by Dan Federman, Agentify Your Swift Repo, which covers building an agent for CI and review feedback. Swift Barcelona has a dedicated YouTube presence, while some groups, like the new MLX India meetup, post event playlists, including a recent talk about using MLX Swift in iOS apps that's worth checking out. And there's even a community-organized Swift Community Meetups YouTube channel, which hosts meetups online and is home to a series of cross-platform Swift talks. These groups support developers in a few ways worth calling out: Local community: they're building local connections among Swift developers and organizations. Room for experimentation: by being less formal and sometimes featuring works in progress, meetups create space to share ideas, get feedback, and learn from one another. I encourage more folks to get involved in their local Swift meetup. And if your group starts publishing content and videos, please share on the Swift Forums in the Community Showcase category. -- Dave Lester Now on to other news about Swift: Videos to watch Interested in using Swift for backend server development? Mohammad Azam posted a livestream recording of Introduction to Hummingbird, a walkthrough of the web framework covering installation and development basics. Meet the Temporal Swift SDK, from Replay 2026, introduces the SDK that brings Temporal's durable workflows (long-running processes that survive crashes, retries, and restarts without losing state) to Swift. The SDK recently reached ## Bringing Goodnotes to the web with Swift and WebAssembly DevFeed: [Bringing Goodnotes to the web with Swift and WebAssembly]() Original publisher: [Read original article]() Author: Yuta Saito Published: 2026-06-01T12:00:00Z Content type: article Language: en Sources: [Swift.org]() Topics: [Swift](), [WebAssembly](), [cross-platform](), [web applications](), [iOS](), [browsers]() Tags: [browsers](), [code](), [cross-platform](), [ios](), [performance](), [swift](), [web-applications](), [webassembly]() ### AI overview Goodnotes describes bringing its existing Swift-based iOS note-taking experience to web browsers by compiling Swift to WebAssembly. The approach reuses a large, performance-critical codebase and preserves consistent ink rendering and behavior across platforms. ### Source excerpt Goodnotes has been helping millions of users take handwritten notes on iPad for over a decade, earning recognition as Apple's iPad App of the Year in 2022. Today, the same Swift code that powers our iOS app also runs seamlessly in web browsers through WebAssembly, delivering the exact same ink rendering and note-taking experience users love. This journey demonstrates that Swift excels as a cross-platform language, running high-performance applications while sharing the same codebase. Every bug fix and improvement to Goodnotes benefits all our users simultaneously, regardless of which platform they use. After two years of development and over two years in production at Goodnotes, we've shown that Swift on WebAssembly is a viable, powerful approach for building complex, performance-critical web applications. Why we chose Swift for the web When we decided to bring Goodnotes to the web in 2021, we faced a critical decision. After more than 10 years of development, we had accumulated millions of lines of Swift code that implemented countless refinements and optimizations for digital ink rendering, document synchronization, conflict resolution using Conflict-Free Replicated Data Types (CRDTs), and content search and document indexing. We need to maintain more than 60 Frames Per Second (FPS) for real-time ink rendering, which makes performance critical. A JavaScript rewrite, Flutter, or Kotlin Multiplatform would all require rewriting our entire rendering engine from scratch, a substantial undertaking that would have delayed our web launch by years and inevitably introduced behavioral differences between platforms. SwiftWasm emerged as the solution. This community-driven project allows Swift code to compile to WebAssembly, running in browsers with good performance. We started experimenting with SwiftWasm, building prototypes to validate the approach. Our first experiment focused on our handwriting component, a performance-critical part of Goodnotes that would serve as a go ## What's new in Swift: April 2026 Edition DevFeed: [What's new in Swift: April 2026 Edition]() Original publisher: [Read original article]() Author: Dave Lester Published: 2026-05-01T10:30:00Z Content type: article Language: en Sources: [Swift.org]() Topics: [Swift](), [Redis](), [Concurrency](), [Caching](), [Open Source](), [releases](), [GitHub]() Tags: [caching](), [concurrency](), [github](), [open-source](), [redis](), [releases](), [server](), [servers](), [swift]() ### AI overview This April 2026 Swift community digest highlights the 1.0 release of valkey-swift, a production-grade Swift client for Valkey and Redis. It covers its Swift 6 implementation, structured concurrency, compile-time typed responses, automatic resource cleanup, command generation, migration from RediStack, documentation, and related Embedded Swift conference talks. ### Source excerpt Welcome to "What's new in Swift," a curated digest of releases, videos, and discussions in the Swift project and community. The 1.0 release of valkey-swift was recently announced on the Valkey blog. We've invited one of the authors to be this month's guest contributor: Hi, I'm Adam Fowler, an open source developer working in the Swift on server ecosystem. I am excited to announce the 1.0 release of valkey-swift - a production-grade Swift client for Valkey. Valkey is a high-performance datastore commonly used as a caching layer or message broker in server applications. It is an open source fork of Redis. Valkey-swift is a client library targeted at Valkey servers but is equally capable of working with Redis. It is built from the ground up with Swift 6 and structured concurrency. Every Valkey command returns typed responses checked at compile time, and strict concurrency checking is enabled throughout so that data races are caught by the compiler, not in production. Connections and subscriptions are all scoped through structured concurrency, so resources clean up automatically. The client covers every standard Valkey command, auto-generated from Valkey's own command specifications to stay in sync as the server evolves. Previously, the de facto client library for Redis was RediStack, which was built on top of pre-concurrency concepts. Retrofitting structured concurrency would have been awkward and some of the new features in valkey-swift infeasible. Around the same time Redis changed its licensing structure and the open source fork Valkey was created. So it felt like a good time to make a clean break and build a new library. If you're building server-side Swift and need a fast key-value store, add valkey-swift via Swift Package Manager, and you're ready to go. If you are using RediStack to connect with a Redis server, we have a guide to help you migrate to valkey-swift. Complete documentation is available, and contributions are welcome on GitHub. Now on to other news a ## Expanding Swift's IDE Support DevFeed: [Expanding Swift's IDE Support]() Original publisher: [Read original article]() Author: Tracy Miranda Published: 2026-04-08T10:00:00Z Content type: article Language: en Sources: [Swift.org]() Topics: [Visual Studio Code](), [cursor](), [AI-assisted coding]() Tags: [cross-platform](), [cursor](), [extension](), [ide](), [swift](), [vs-code]() ### AI overview Swift's official VS Code extension is now available through Open VSX, extending Swift support to compatible editors such as Cursor, VSCodium, Kiro, and Antigravity. ### Source excerpt You can now write Swift in a broader range of popular IDEs, including Cursor, VSCodium, AWS's Kiro, and Google's Antigravity. By leveraging VS Code extension compatibility, these editors tap directly into the Open VSX Registry, where the official Swift extension is now live. Swift has long supported development using multiple IDEs including VS Code, Xcode, Neovim, and Emacs. Swift is also compatible with editors that implement the Language Server Protocol (LSP). This growing ecosystem of editor support is particularly significant as Swift continues to show its versatility across platforms and development environments, including agentic IDEs. Swift on Open VSX The Swift extension for VS Code is now officially available on the Open VSX Registry, the vendor-neutral, open source extension registry hosted by the Eclipse Foundation. The extension adds first-class language support for projects built with Swift Package Manager, enabling seamless cross-platform development on macOS, Linux, and Windows. This milestone brings Swift support, including code completion, refactoring, full debugging support, a test explorer, as well as DocC support, to a broader ecosystem of compatible editors and allows agentic IDEs like Cursor and Antigravity to automatically install Swift, with no manual download required. Swift in Cursor, powered by the Swift extension on Open VSX. Get Started To start using the Swift extension in any Open VSX-compatible editor, simply open the Extensions panel, search for 'Swift' and install the extension. If you're using Cursor, getting started is easier than ever. Check out our new dedicated guide: Setting up Cursor for Swift Development. It walks you through the setup, features and includes how to configure custom Swift skills for your AI workflows. Swift now has support for a wider range of modern editors and IDEs to meet developers where they are. Download the extension, try it out in your editor of choice, and don't forget to share your feedback! ## What's new in Swift: March 2026 Edition DevFeed: [What's new in Swift: March 2026 Edition]() Original publisher: [Read original article]() Author: Dave Lester Published: 2026-03-31T14:30:00Z Content type: article Language: en Sources: [Swift.org]() Topics: [Swift](), [cross-platform](), [releases](), [Tooling](), [Linux](), [Windows](), [systems](), [Containers](), [Concurrency](), [Jetson](), [real-time](), [ASP.NET Core]() Tags: [ai](), [announcement](), [concurrency](), [cross-platform](), [developer](), [ecosystem](), [jetson](), [linux](), [news](), [open-source](), [platform](), [programming](), [real-time](), [releases](), [swift](), [systems](), [tooling](), [windows]() ### AI overview A March 2026 digest of Swift project and community news, led by Swift 6.3 and the ongoing integration of Swift Build with Swift Package Manager. It also highlights cross-platform build support, open-source package testing, community talks, systems programming, real-time computer vision on NVIDIA Jetson, a Vapor-based AI data pipeline, Swift Concurrency, and API deprecation practices. ### Source excerpt Welcome to "What's new in Swift," a curated digest of releases, videos, and discussions in the Swift project and community. Swift 6.3 has been released, expanding Swift into new domains and improving developer ergonomics. A highlight of its release is work to improve cross-platform build tooling. Owen Voorhees shares an update on that effort: Hi! I'm Owen, a lead engineer on the Core Build team at Apple. Last year we shared our goal to bring Swift Build to Swift Package Manager, in an effort to deduplicate build technologies within the Swift ecosystem and deliver a consistent build experience across all platforms that Swift supports. Since the announcement, we've been working in the open, landing hundreds of patches to improve Swift Build's support across various platforms including Linux and Windows, and to integrate it deeply in Swift Package Manager. With Swift 6.3, developers have the option to enable this integration and try it out with their packages. To validate parity with the previous build system, we've used the package list from swiftpackageindex.com, testing thousands of open source packages with Swift Build. Most recently, the main branch of Swift started using Swift Build as its default build system, paving the way for Swift Build to be the out-of-the-box option for Swift developers in a future Swift release. Over the coming months, we'll continue sharing our progress and driving down the remaining bugs to bring the build system to parity. We encourage you to give it a try and file bugs that you encounter. We're excited by this progress, and look forward to building future tooling improvements across all platforms and project models that will benefit from this build system. Now on to other news about Swift: Videos to watch Interested in Swift for systems programming? The -ization of Containerization, presented at SCaLE, covers the Containerization project and their experience adopting Swift. Swift community meetup #8 featured two talks: real-time compu ## Swift 6.3 Released DevFeed: [Swift 6.3 Released]() Original publisher: [Read original article]() Author: Joe Heck Published: 2026-03-24T10:00:00Z Content type: release Language: en Sources: [Swift.org]() Topics: [Swift](), [c/c++](), [cross-platform](), [Android](), [Embedded Software Dev](), [Optimization](), [Tooling]() Tags: [android](), [c](), [c-c-plus-plus](), [cross-platform](), [embedded](), [optimization](), [swift](), [tooling]() ### AI overview Swift 6.3 expands Swift across the software stack with improved C interoperability, cross-platform build tooling, embedded-environment support, and an official Swift SDK for Android. The release also adds module selectors and new controls for compiler optimizations. ### Source excerpt Swift is designed to be the language you reach for at every layer of the software stack. Whether you're building embedded firmware, internet-scale services, or full-featured mobile apps, Swift delivers strong safety guarantees, performance control when you need it, and expressive language features and APIs. Swift 6.3 makes these benefits more accessible across the stack. This release expands Swift into new domains and improves developer ergonomics across the board, featuring: More flexible C interoperability Improvements to cross-platform build tooling Improvements for using Swift in embedded environments An official Swift SDK for Android Read on for an overview of the changes and next steps to get started. Language and Standard Library C interoperability Swift 6.3 introduces the @c attribute, which lets you expose Swift functions and enums to C code in your project. Annotating a function or enum with @c prompts Swift to include a corresponding declaration in the generated C header that you can include in your C/C++ files: @c func callFromC() { ... } // Generated C header void callFromC(void); You can provide a custom name to use for the generated C declaration: @c(MyLibrary_callFromC) func callFromC() { ... } // Generated C header void MyLibrary_callFromC(void); @c also works together with @implementation. This lets you provide a Swift implementation for a function declared in a C header: // C header void callFromC(void); // Implementation written in Swift @c @implementation func callFromC() { ... } When using @c together with @implementation, Swift will validate that the Swift function matches a pre-existing declaration in a C header, rather than including a C declaration in the generated header. Module name selectors Swift 6.3 introduces module selectors to specify which imported module Swift should look in for an API used in your code. If you import more than one module that provides API with the same name, module selectors let you disambiguate which API to use: ## Swift at scale: building the TelemetryDeck analytics service DevFeed: [Swift at scale: building the TelemetryDeck analytics service]() Original publisher: [Read original article]() Author: Daniel Jilg Published: 2026-03-06T11:00:00Z Content type: article Language: en Sources: [Swift.org]() Topics: [Swift](), [Vapor](), [Back end](), [API](), [Containers](), [Kubernetes](), [App](), [data](), [Open Source](), [iOS](), [Python](), [Ruby]() Tags: [analytics](), [api](), [apis](), [architecture](), [backend](), [containers](), [data](), [json](), [kubernetes](), [open-source](), [swift](), [web]() ### AI overview TelemetryDeck describes how it built a privacy-focused analytics service on Swift. The article covers its use of Vapor for scalable APIs and services, Kubernetes-hosted containers, Swift-native service connectors, and the performance and efficiency benefits of Swift for a high-volume backend. ### Source excerpt TelemetryDeck is an app analytics service specifically for developers, designed to manage usage analytics that are anonymized, privacy-focused, and really easy to use. TelemetryDeck is managing the data of over 16 million people every month, helping thousands of app publishers improve their products, and we're doing it all with a Swift-based infrastructure. The decision to go with Swift brought a lot of unexpected advantages for us. We come from a world of iOS in the frontend, Python, Node, or Ruby in the backend for server-based applications. Compared to these languages and frameworks, Swift is just as easy to use, and its compiled nature allows us to catch a lot of possible errors at compile time instead of runtime, making it ideal for a hardened, high-performance web service. Let me share our journey and history with you. Adopting Swift for backend services TelemetryDeck is built on Vapor, a web framework written in Swift, for building scalable APIs and services. Similar to other Vapor-based projects like Things, TelemetryDeck runs on containers hosted in Kubernetes. Our metadata lives in Postgres, and our analytics data is stored in Apache Druid. We use Swift-native connectors to access APIs for these services. Some of those come from the Swift community, others we've written ourselves and are giving back to the open source ecosystem. In the very beginning, when TelemetryDeck was just a little exploratory hobby project, we wanted to go with Swift on the server simply because we love Swift, and we're pretty decent at it. Vapor was new, and we figured, let's try this out and learn a new way to apply and combine our skills. In the end, this decision turned out to be exactly the right one and resulted in a lean architecture that is highly performant, stable, and allows us to develop and iterate quickly. Swift's performance characteristics are remarkable, especially in multithreading. Python's Global Interpreter Lock has long constrained true parallelism, though rece ## What's new in Swift: February 2026 Edition DevFeed: [What's new in Swift: February 2026 Edition]() Original publisher: [Read original article]() Author: Dave Lester Published: 2026-03-02T14:05:00Z Content type: news Language: en Sources: [Swift.org]() Topics: [releases]() Tags: [apis](), [community](), [concurrency](), [conference](), [databases](), [open-source](), [process](), [sql](), [swift](), [webassembly]() ### AI overview A Swift community roundup covering FOSDEM participation, browser-based Swift with WebAssembly, and new packages for fuzzy matching, GraphQL APIs, SQL Server access, terminal UIs, and system metrics. ### Source excerpt Welcome to this edition of "What's New in Swift," where we share interesting projects and updates in the Swift community that deserve visibility to a broader audience. FOSDEM is the largest open source conference in the world, and this year Swift was featured in talks across multiple tracks and a dedicated pre-conference event. Here's a report from the Swift community: Hey there! Karen Chu here. 👋 I help grow and support the Swift open source community, and one of my favorite things has been increasing Swift's participation in open source events. As a follow-up to Swift's presence at FOSDEM last year, this year we expanded our approach by running our own Pre-FOSDEM fringe event, which included 11 talks across multiple platforms, in addition to four Swift talks across various devroom tracks. Though it was my first year at FOSDEM, it was delightful to meet several people who attended the Swift devroom last year and also came through again this year. With the vast array of attendee backgrounds (I met recent grads, former Swift mentees, Swift workgroup members, folks from the Swift Core Team, and more) and talks covering different platforms (embedded, server, BSD, Android, and more), that weekend showed me just how much momentum Swift has gained as a general purpose language that can benefit everyone. I wanted to highlight Simon Leeb's talk, Swift in the Browser with ElementaryUI, as a popular talk from the event which showed how to run Swift applications natively in the browser with WebAssembly. FOSDEM may be over (for now), but I'm already excited about how the Swift community will show up next year! To catch up on all the talks at the Pre-FOSDEM event, check out the YouTube playlist. Now on to other news about Swift: New package releases Originally developed for searching financial databases for strings like stock tickers, FuzzyMatch brings high-performance fuzzy string matching to Swift. Now you can expose GraphQL APIs in your applications with new Vapor and Humming ## Announcing Swift System Metrics 1.0: Process-Level Monitoring DevFeed: [Announcing Swift System Metrics 1.0: Process-Level Monitoring]() Original publisher: [Read original article]() Author: Vladimir Kukushkin Published: 2026-02-20T10:00:00Z Content type: release Language: en Sources: [Swift.org]() Topics: [Swift](), [Monitoring](), [Processes](), [observability](), [cpu](), [Grafana](), [Linux](), [macOS](), [API](), [OpenTelemetry](), [Prometheus](), [real-time]() Tags: [contributed](), [cpu](), [grafana](), [how-to](), [linux](), [macos](), [metrics](), [monitoring](), [net](), [observability](), [opentelemetry](), [performance](), [process](), [prometheus](), [real-time](), [release](), [swift]() ### AI overview Swift System Metrics 1.0 is a stable Swift package for collecting process-level metrics, including CPU utilization, memory usage, file descriptors, and process start time, on Linux and macOS. It integrates with Swift Metrics and supports Prometheus and OpenTelemetry backends, with an example Grafana dashboard and production-focused observability use cases. ### Source excerpt We are excited to announce the 1.0 release of Swift System Metrics, a Swift package that collects process-level system metrics like CPU utilization time and memory usage. Swift System Metrics runs on both Linux and macOS, providing a common API across platforms. Swift System Metrics visualized in Grafana, demonstrating what's possible with real-time monitoring. Monitoring process metrics enables you to detect performance issues, optimize resource usage, and ensure your service remains reliable and cost-effective under varying loads. You can integrate Swift System Metrics into your service in just a few lines of code, making observability accessible to every developer and ensuring that even the smallest services can have production-grade visibility from day one. Swift System Metrics is part of a larger set of packages that provide an end-to-end solution for integrating metrics into your Swift applications and services. Once system metrics are collected, they're reported to Swift Metrics, a backend-agnostic metrics API that can work with popular backends like Prometheus and OpenTelemetry. Swift System Metrics also leverages Swift Service Lifecycle to handle process bootstrapping and resource cleanup. With the 1.0 milestone, the API is now stable and ready for use. Note that this package was previously swift-metrics-extras, and renamed to better reflect its purpose. Highlights Collects and reports: CPU utilization time Virtual and resident memory usage Open and maximum available file descriptors Process start time API-stable public interface Support on both Linux and macOS musl libc compatibility The package includes an example Grafana dashboard configuration to start visualizing metrics immediately. Get Started Add the dependency to your Package.swift: .package(url: "https://github.com/apple/swift-system-metrics", from: "1.0.0") Add the library dependency to your target: .product(name: "SystemMetrics", package: "swift-system-metrics") Import and use in your code: impo ## What's new in Swift: January 2026 Edition DevFeed: [What's new in Swift: January 2026 Edition]() Original publisher: [Read original article]() Author: Dave Lester Published: 2026-01-30T15:15:00Z Content type: article Language: en Sources: [Swift.org]() Topics: [Swift](), [web applications](), [Web](), [Deployment](), [Tooling](), [PHP](), [Python](), [Code](), [Cloud](), [Linux]() Tags: [applications](), [business](), [code](), [deployment](), [developer](), [engineering](), [performance](), [php](), [python](), [server](), [swift](), [tooling](), [web](), [web-applications]() ### AI overview Swift is presented as a successful choice for building production web applications, with strong reliability, performance, and code quality. The article also highlights the challenges of recreating build and deployment tooling and compares the experience with PHP and Python. ### Source excerpt A Reddit thread earlier this month asked about building web apps with Swift. For this edition of "What's new in Swift," we invited a developer to share their experience: Hi, I'm Nick Sloan. I'm the head of engineering at Studioworks, a platform that makes it easy and fun to run your creative studio, agency or freelance business. We chose Swift for Studioworks because of how easy it is to write safe and reliable code with great performance. Our Swift project makes use of Hummingbird 2, Soto (for its incredible DynamoDB Codable support), Hummingbird MacroRouting, and Elementary. Studioworks is a big and growing project. We are the largest Elementary codebase, and I suspect we are among the biggest projects using Hummingbird as well. We've already processed millions of dollars in invoices for our customers, and after 20 years of shipping web applications, I have never seen fewer crashes and bugs make it to production. Performance has also been excellent, especially after moving our templates to Elementary. Our heaviest pages make it to the browser in less than 100ms. We've been deploying web applications with PHP and Python for decades, and getting started with a Swift web project was certainly a bit slower. We had to recreate some of the build, deployment and chat tooling we had been relying on in our Python projects for years, and it took us a bit of experimenting to realize that Elementary was the best choice for templating. Once we got past those hurdles we've been able to build about as fast as we ever did with Python, and the quality is much better. Swift on the web has been a resounding success for us, and I hope we'll see this part of the community continue to grow! -- Nick Sloan Learn more about Swift on Linux and server-based use cases by checking out our October edition, which featured highlights from the Server-Side Swift Conference. The swift.org website also has a use case page dedicated to cloud services, including a tutorial to get started. And now for w ## Announcing the Windows Workgroup DevFeed: [Announcing the Windows Workgroup]() Original publisher: [Read original article]() Author: Mishal Shah Published: 2026-01-26T12:00:00Z Content type: article Language: en Sources: [Swift.org]() Topics: [Swift](), [Windows](), [Programming](), [API](), [interoperability](), [VS Code Extension]() Tags: [announcement](), [api](), [community](), [contributors](), [extension](), [interoperability](), [swift](), [vs-code](), [windows]() ### AI overview Swift has announced a community-led Windows workgroup focused on maintaining and improving Swift support for Windows application development. ### Source excerpt We are excited to announce the creation of the Windows workgroup! The primary goal is to ensure ongoing support for Swift on Windows, enabling users to develop Windows applications using the Swift programming language and its associated tools. The new Windows workgroup joins a growing list of Swift workgroups, including the Android workgroup, Build and Packaging workgroup, and Testing workgroup which were all added in the past year. Swift workgroups are community-led efforts, formally recognized by the project, to help move forward key areas. Windows has been an officially supported platform since 2020, and there's been great progress since then. The VS Code extension supports Windows, and we've seen the community take advantage of Swift's features on Windows, some of which are described in a 2023 blog post about Using Interoperability to Build on Windows. The workgroup will build upon these efforts and focus on work to: Improve and maintain Windows support for the official Swift distribution. Recommend enhancements to core Swift packages such as Foundation and Dispatch to work better with Windows idioms. Make recommendations to the Swift Project about the direction of future Windows support in Swift. Identify and recommend best practices for bridging between Swift and the Windows API, and for shipping Swift libraries with Windows applications. To learn more and get involved: Discuss this announcement on the forums, and share ideas in the Windows category. Learn more about the Windows workgroup by reading its charter. Join the Windows workgroup's meetings every other Wednesday at 9:00 AM PT (Pacific Time Zone). Workgroup membership and meetings are open to those who wish to participate, and contributors are welcome! To receive an invite, send a message to @windows-workgroup on the Swift forums. ## Improving the usability of C libraries in Swift DevFeed: [Improving the usability of C libraries in Swift]() Original publisher: [Read original article]() Author: Doug Gregor Published: 2026-01-22T12:00:00Z Content type: tutorial Language: en Sources: [Swift.org]() Topics: [Swift](), [interoperability](), [API](), [webgpu](), [Code]() Tags: [api](), [blog](), [c](), [code](), [interoperability](), [swift](), [usability](), [webgpu]() ### AI overview This tutorial explains how to make C libraries feel safer and more idiomatic when used from Swift. Using WebGPU C headers as an example, it shows how Swift annotations can expose argument labels, methods, enums, and automatic reference counting without modifying the underlying C implementation. ### Source excerpt There are many interesting, useful, and fun C libraries in the software ecosystem. While one could go and rewrite these libraries in Swift, usually there is no need, because Swift provides direct interoperability with C. With a little setup, you can directly use existing C libraries from your Swift code. When you use a C library directly from Swift, it will look and feel similar to using it from C. That can be useful if you're following sample code or a tutorial written in C, but it can also feel out of place. For example, here's a small amount of code using a C API: var instanceDescriptor = WGPUInstanceDescriptor() let instance = wgpuCreateInstance(&instanceDescriptor) var surfaceDescriptor = WGPUSurfaceDescriptor() let surface = wgpuInstanceCreateSurface(instance, &surfaceDescriptor) if wgpuSurfacePresent(&surface) == WGPUStatus_Error { // report error } wgpuSurfaceRelease(surface) wgpuInstanceRelease(instance) The C library here that Swift is using comes from the webgpu-headers project, which vends a C header (webgpu.h) that is used by several implementations of WebGPU. WebGPU is a technology that enables web developers to use the system's GPU (Graphics Processing Unit) from the browser. For the purposes of this post, you don't really need to know anything about WebGPU: I'm using it as an example of a typical C library, and the techniques described in this blog post apply to lots of other well-designed C libraries. The Swift code above has a very "C" feel to it. It has global function calls with prefixed names like wgpuInstanceCreateSurface and global integer constants like WGPUStatus_Error. It pervasively uses unsafe pointers, some of which are managed with explicit reference counting, where the user provides calls to wpuXYZAddRef and wgpuXYZRelease functions. It works, but it doesn't feel like Swift, and inherits various safety problems of C. Fortunately, we can improve this situation, providing a safer and more ergonomic interface to WebGPU from Swift that fee