[monaghanboy]

Another major version was again released? Seems like literally just a few months ago when, just after upgrading my team's codebase to Webpack 2, Webpack 3 came out.

Why do front-end application frameworks (e.g. Angular, and even React) and build tools constantly feel the need to reinvent what they just reinvented? Don't people (users and developers alike) recognize and tire of the churn?

Stepping back though, a thread like this appears on HN at least once every few months, so I guess this is just par for the course.

[franciscop]

Because they learn from mistakes and can make it better the next time! That happens everywhere; except JS world (at least with npm) is very, very new (relatively speaking). Also now there are many more devs than when the older languages came out, so the experimentation is a lot wider.

[vanderZwan]

> Because they learn from mistakes and can make it better the next time!

Well, except seemingly learning from the mistakes made when introducing breaking changes.

I not being a cynical jerk bashing on WebPack in particular here. I use it every day and am grateful for its existance, and look forward to the point where migrating to version 4 is going to be relatively painless, at which point I'll actually give that another try.

But on the whole, it's like nobody in the JS world seems to learn from the mistakes of other JS projects and they have to make them again themselves.

[nl]

I'm not convinced that this is true.

In the JS world different layers feel very closely bound and it isn't usually clear at all how to leave out things which are (mostly at some level) optimisations.

That isn't great when things go wrong.

[darepublic]

I am staying with webpack ~2 for now, it does everything I need it to do