Next.js 11.1

[Eric_WVGG]

"these changes in front-end frameworks makes everything slower" everyone starts screaming

"these changes in front-end frameworks makes everything bonkers faster" chirps

kudos to the Next team doing the good work

[leerob]

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

[dmitryminkovsky]

My thoughts exactly. Was surprised this wasn’t on the homepage.

[rektide]

this take is singe-ing but I think it ellucidates a truth that the vast arrayed pissed off scared vocal anti-web-progress retrogressionist amassing un-silent minorities are so pissy about:

we have only just started getting good at the web. the web is still ripe, still, exciting, still heavily heavily optimizable & usable for the cuttingest of cutting edgest computing & computing experiences.

look: the web is often poorly utilized. the folks making money have been doing so at great cost to the user for a long time, on one hand, and the tech itself is still radically underexplored, under tried, under utilized, and most companies use cookie cutter massified software development tools that radically constrain what systems they might produce. they refuse to think.

but some people do think. they have some good thoughts. they reconsider what these platforms might be used to enable, rethink how to assemble experiences from this base matter, from these first toolkits. kudos to everyone still engaged with working the web towards better: we have so much to find out, so much to try, to tune, to evolve along, and we need diverse spirit of all kinds of efforts trying for better. that's why the web keeps winning. because the tool kit can, because the web is low level, because it permits endless platform & architectural engineering atop it's simple & long long long enduring media form.

[pull_my_finger]

I'm really not a fan of the next/image component at all. It's so unintuitive to use.

[leerob]

Hey, sorry about this. What could we do better?

[willio58]

Interested in what’s the issue here, next.js’s image component has been amazing and a breeze for me so far.

[Thomaschaaf]

Why was SWC chosen instead of esbuild? I see esbuild in a lot more places.

Also with the developer of SWC joining next.js will the non-open-source parts (STC)[1] be released?

[1]: https://stc.dudy.dev/

[cercatrova]

Because they "strongly believe Rust is the future of JS tooling." I'd agree honestly, I like Rust a lot more than Go. But that's a debate for another time.

https://news.ycombinator.com/item?id=28157256

[bern4444]

My cursory knowledge is Go is best for distributed services and things that heavily involve the network.

Rust is better for memory based operations due to its safety and speed.

[ostenning]

I personally would love to see better i18n routing in nextjs. Supporting translated routes while routing to the same page, e.g: /project, /projekt and /projet for en, de and fr

[bilater]

Noob question but when they say ES Modules support will be integrated does that mean for the server side stuff / serverless functions?

[kylegalbraith]

I'm a fan of the improvements made to next/image!

[presentation]

Hm, does the switch to SWC impact babel config support?

[leerob]

With 11.1, SWC support is still experimental (we haven't enabled it by default). In the next release when this becomes stable (and replaces Babel), we will provide more guidance and examples. If you have an existing custom Babel configuration, you'll still be able to de-optimize and "eject" from SWC and continue using Babel. This ensures we don't break existing applications and make it easier to incrementally adopt these new performance improvements.

[adursun]

Next.js is getting better every day!