The only two tools I like in the JS world is `yarn` and `prettier`. They're focused and do what they do well. But you add eslint and any of the others and their configuration is a full fledged turing machine. Even autotools feels nice in comparison to that mayhem.
I agree that ESLint can become a mess, which is why I'm ok with a new competitor that doesn't require the extra configuration. Sure: they're also replacing Prettier (unnecessary) but everyone can keep using Prettier and change if Oxfmt ever becomes better.
All the other tools here are either existing, or drop-in replacements.
The current version of webpack was released 5 years ago. You can keep using eslint 8 which was released 4 years ago. This really isn’t the constantly changing space it was in the 2010’s
You will certainly be able to compile it. You might have hard time updating it though.
Updating is a different matter, if you're using multiple tools, hundreds of packages and several configuration files.
Which is why a unified tool that doesn't require configuring 20 tools at once is a good idea IMO.
This is like the comment version of the gish gallop.
And I gave three other examples, and I can give others: React itself has been around for 12 years, leading. Vue has been super stable too.
Migrating versions of frameworks is several magnitudes harder than migrating the ESLint config, and ESLint is optional. Migrating versions of previous tooling like Babel or Webpack is several orders of magnitude more complicated than ESLint.
Sure it would be better if people had gotten it right the first time, but the fatigue problem isn't really due to React.
And my argument isn't that "X is better than Y". It's that the number of new tools showing up is WAY smaller than it was when those complaints started. Today it has become a meme here in HN, often by people outside the frontend community.
But now there’s no unifying principles behind anything. No conventions. It’s just incantations to get thing working nicely together. It’s all preprocessing and post processing, code generation an what not.
Everything else is smooth and silk
Ohh, yes eslint 8 => 9 migration were also a big pain to handle.
Still not resolved. Their main recommended config is still not updated for 9.
Like, their decision to change configuration format in a way that breaks all and every plugin, tutorial, project in existence as a giant "fuck you" to the whole ecosystem and all web developers of the world - isn't that a reason good enough to never come back at this tool ever again?
It wasn't there X years ago and had changes to the config Y years ago that were very annoying time-consuming. One can believe that single digits of X and Y are "not stable enough" with a simple reason that you live in Decenarian Math.
For all its warts and all the hate that it gets, at least autotools is stable and not introducing breaking changes.