"these changes in front-end frameworks makes everything bonkers faster" chirps
kudos to the Next team doing the good work
Thanks a lot for Next.js and the Vercel platform. Both are great.
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...
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.
who gives a crap about esm? you need to have it. bundlers that arent shitty bloated slow beasts? good yes, but to me not a tuallyuch of a difference h my hot reload was under 2s before, usually I didn't even bother & suffered a full 5s progressive recompile. shaving those seconds off is a distraction from architectural redefinition of the core constituating elements of web which is the real ongoing game afoot. value? oh sure, by eliminating inefficiency, but not fundamentally progressive: a way to do more faster.
While I'm at it, next/link also had some bonkers defaults such as the link prefetching on view instead of on hover (neither of which could be disabled, either…).
I hope all that is getting some attention soon. If I can offer some frank feedback: I've had an overall positive experience with the framework, but there have been clear quality issues here and there and I'm always concerned when I see a large feature churn without a high amount of attention being put into existing bugs.
I filed three bugs while porting an app over half a year ago (https://github.com/vercel/next.js/issues/20984, https://github.com/vercel/next.js/issues/21474, https://github.com/vercel/next.js/issues/21461). None of them have even been acknowledged by a dev yet. (That last one was a doozy, too; I'm not actually sure it's a nextjs bug)
Also with the developer of SWC joining next.js will the non-open-source parts (STC)[1] be released?
Rust is better for memory based operations due to its safety and speed.
If you are using tools like swc or esbuild, then you need to evaluate tool itself, not the language it was written in.
Similarly here, evaluating esbuild vs swc inherently involves comparing their capabilities, benefits, potential etc. A lot of that is informed by the language its written in.
