21–30 of 106 posts
The next-gen bundler rewrites are getting insane, just as things were consolidating in the other parts of JS. We now have: - EsBuild - SWC (also written by someone who works at Vercel) - TurboPack - Vite (rollup) - Parcel - Rome I've noticed in the javascript ecosystem there is much less convergence than in other languages. Everyone wants a flag in the ground.
Their tutorial is incredible, everyone should take a lesson from Vercel on this: https://nextjs.org/learn/foundations/from-react-to-nextjs/ge... Tell me: 1. What I need to know to understand this documentation 2. The before state (plain React.js) 3. The after state (Next.js) I'm fucking sold, I'm going to use Next.js just based on how well written this documentation is.
The next-gen bundler rewrites are getting insane, just as things were consolidating in the other parts of JS. We now have: - EsBuild - SWC (also written by someone who works at Vercel) - TurboPack - Vite (rollup) - Parcel - Rome I've noticed in the javascript ecosystem there is much less convergence than in other languages. Everyone wants a flag in the ground.
Right now you can stay with Webpack or whatever you were using already, or you can try one of the new shiny things if you want to. But if you want to avoid the churn, it's probably time to just wait for a bit until things settle down.
The next-gen bundler rewrites are getting insane, just as things were consolidating in the other parts of JS. We now have: - EsBuild - SWC (also written by someone who works at Vercel) - TurboPack - Vite (rollup) - Parcel - Rome I've noticed in the javascript ecosystem there is much less convergence than in other languages. Everyone wants a flag in the ground.
The next-gen bundler rewrites are getting insane, just as things were consolidating in the other parts of JS. We now have: - EsBuild - SWC (also written by someone who works at Vercel) - TurboPack - Vite (rollup) - Parcel - Rome I've noticed in the javascript ecosystem there is much less convergence than in other languages. Everyone wants a flag in the ground.
That's a good thing? Keeps things fresh and keeps established "norms" unable to stay complacent.
// "alt" is now required for improved accessibility I'm all for accessibility, but let us decide when to implement it.
You should still be able to use alt="" to indicate that it is "decorative" and not meaningful imagery for a visually-impaired user.
// "alt" is now required for improved accessibility I'm all for accessibility, but let us decide when to implement it.
> I'm all for accessibility, but let us decide when to implement it. Which usually means never.
// "alt" is now required for improved accessibility I'm all for accessibility, but let us decide when to implement it.
> I'm all for accessibility, but let us decide when to implement it. Which usually means never.
See also (naming things): https://twitter.com/secretGeek/status/7269997868
The next-gen bundler rewrites are getting insane, just as things were consolidating in the other parts of JS. We now have: - EsBuild - SWC (also written by someone who works at Vercel) - TurboPack - Vite (rollup) - Parcel - Rome I've noticed in the javascript ecosystem there is much less convergence than in other languages. Everyone wants a flag in the ground.
Beauty of nextjs though is that you don't have to worry about it unless you want to go under the hood. My quality of life has improved tremendously since I stopped having to deal with webpack config files, and upgrading to the hottest bundler on the street couldn't be lower on my list of priorities.