re: "is it the tool or is it developers using it wrong" it's clearly the tool(s). It's like the JS scene can't leave well enough alone and must constantly reinv

re: "is it the tool or is it developers using it wrong" it's clearly the tool(s). It's like the JS scene can't leave well enough alone and must constantly reinvent everything, and anyone who preaches restraint is regarded as a luddite who "just doesn't get it." I mostly blame the "JS thought leaders" i.e. people who should know better. They hype one tool after the next with little to no concept of the cost of obsolescence (having to throw out your 2 year old new web app), which is yet another major issue with JS hype. Then employers ask for the tool, then devs _have to_ learn the tool whether they want to or not if they want to match job descriptions. Everyone's afraid of "falling behind" and as a consequence everyone rushes headlong. Ironically, given that this article is about DX, the JavaScript ecosystem has in recent years been regarded by many as an insane mess of infinite complexity, majorly frustrating many developers who have jobs besides just learning (or teaching) new frameworks. That is to say, I don't think these costs have even bought us good DX. They've bought a "lowest common denominator" environment where you can hire a new dev bootcamp grad to build your website and your app quickly and cheaply and agile-ly and quickly and cheaply and... did I say quickly? Nevermind the mess you'll spend years cleaning up. Summary: JS (and beyond) thought leaders & framework authors are selling silver bullets and businesses just can't say no.