Hacker News Reader

Comment by leerob | Hacker News Reader

Thank you! We strongly believe Rust is the future of JS tooling[1] and will be investing heavily in this ecosystem. It's been in the works for awhile[2] and I'm happy to start seeing these changes land in Next.js. `npm i next@latest` for perf improvements every time is the goal!

[1]: https://twitter.com/rauchg/status/1417861178290851842

[2]: https://twitter.com/rauchg/status/979525321882984448

View on HN

Hadn’t heard of SWC, only esbuild. Why did your team choose SWC/rust over esbuild/go? This: https://mobile.twitter.com/rauchg/status/979525321882984448 ?

Thanks a lot for Next.js and the Vercel platform. Both are great.

We chose SWC over esbuild for a few reasons:

1. SWC is designed to be extensible. We can use it as a crate with no forks! [1]

2. We love the Rust ecosystem. Stellar community & WASM support. Excellent long-term performance prospects (like total control over memory management).

[1]: https://github.com/padmaia/next.js/blob/cf1d081c5b2f55085ceb...

Seems reasonable decision but for me it increases the barrier to contribute. I already learning Go to contribute to some projects

We're planning to try and release learning material around Rust!

So is SWC integrated in 11.1? Or is it still _being_ integrated? As in, will I see the performance improvements from SWC by upgrading, or is this just the groundwork for it to be more widely integrated?

Still being integrated - the next release will have a flag you can turn on.

Reply on news.ycombinator.com