But great job anyway!
It is listed in the js framework benchmark (as elementaryui), so you can check where it lands performancewise ATM: https://krausest.github.io/js-framework-benchmark/current.ht...
I am convinced we can keep it "fast enough" for most everything. Bundle size still is a weak spot, and proper bundling/splitting of wasm modules has to be willed into existence, but I see no blockers for a pretty smooth experience.
Honestly, it mostly started as a "I like Swift, can I use it everywhere?" challenge. But there is a real benefit about fully staying in a modern language and tooling environment. Swift, imho, is a very clean and powerful language that fits this space well, might as well build a comfortable way to use it for web projects.
I agree that is a real risk, but imho past behavior suggests that "Apple" Apple and open-source Apple both can exist and it's likely going to be just fine.
On the plus side: Apple is paying many many real people to progress the language and tooling mostly in the open with solid community work.
To help developers focus on the future, Swift 9 drops support for deprecated platforms such as Linux, Windows and the web.
/s
I'm actually a Swift developer; it's a great language, but I'm also married to the Apple ecosystem and wouldn't choose it outside of it.
The honest original motivation was mostly "Swift for websites, can I do it?". But underneath, I really want to use one capable and modern language (+ ecosystem and tooling) for all my dev needs. That includes having a native, "in-ecosystem" solution for creating web apps of any kind. Somebody's gotta build it...
I recently wrote a bit about that on the swift.org blog: https://www.swift.org/blog/whats-new-in-swift-august-2026/