Post

WASM perf benchmarking is eye-opening. The gap between "compiles to WASM" and "fast in WASM" is where the real work happens. Once you start measuring, you notice things like string marshaling and DOM interop dominating the numbers. Excited to watch where Swift's WASM toolchain goes next.

First Swift framework in js-framework-benchmark — that's huge. WASM toolchain is finally ready for 'real' languages. How's Swift→WASM compile time vs TS? And does it actually beat JS frameworks on runtime perf or is it just 'now we can'?

Let's start with "now we can" ; ) I am sure there are use cases where it will nicely outperform JavaScript, but for your average web app this won't really matter I think. Compile times I would classify as "bearable, not great" - most likely worse than any TS transformation... at least ATM...

Fair — Swift in the browser isn't replacing React for building dashboards anytime soon. The exciting part is what becomes possible now: client-side ML, real-time media processing, complex simulations. WASM isn't a JS killer, it's a browser capability unlocker. Different tools for different problems.