No telling how many sides the next iteration of the wheel may have but one thing's for certain: That one will be the ultimate version.

Well at least Vite does not lock you in the Next.js eco-system, so it's something ¯\_(ツ)_/¯.

Overall the community is starting to embrace better languages for tooling, primarily Rust with some Go and Zig sprinkled in. Eventually I think we will hit a point where there will be a defacto dev tool that can take a web app and package it however you want, deploy it wherever you want, and do it very quickly. Some would argue those exist now, but until it can be done literally everywhere, painlessly, I would contend we aren't there yet. It's probably more likely something like WASM/WASI takes over before then honestly.

What I hate about javascript fatigue is that there's never enough time for something to mature before it gets replaced. Documentation always covers the basic scenarios and never any edge cases. Sooner or later you end up trying to find a solution in a github issue 20 pages down.

I think webpack is a special exception. It somehow revised the whole 5 major version and still don't get a proper plugin development document at all, not even basic one. You don't even have a flow graph that tells you events happen in which order. Everyone either Google and copy paste random example or reading the source by themselves.

It always amazed me that such a big project can just live without docs.

that's the only thing agile people got from the manifesto

an excuse not to write docs, ever

it's endemic in the majority of companies I've seen in the last 10 years

hopefully tooling (eg. docs.rs mostly automatically generated and pleasant to use) will help in the long term