[krapp]

Modern web development has also created its share of problems. Needing to import 20 JS files and manage namespaces isn't a problem anyone had before the JS community decided every "library" had to consist of only a single function rigged to an entire test suite with an arbitrarily deep dependency tree. Sure, finding libraries, adding them in script tags and uploading them directly to the server (or linking to a CDN) wasn't as convenient as using a package manager, but vast sections of the web didn't stop working because a repo got pulled or because the SPOF repository for the language went down.

And then you have compile-to-js languages like Typescript, and the entire paradigm of "javascript as bytecode" which, for all of their benefits in adding safety, also added exponential complexity. Frontend frameworks with their own unique paradigms that generate HTML and CSS entirely in JS, and ignore the separation of concerns the web is actually built around.

All of these have their place and their value, but the fact that "vanilla JS" is coming back as a trend might be a sign that things have strayed a bit too far in the wrong direction.

[johnfn]

I think it's just two camps. The vanillajs camp is people mostly working on their own, who can't imagine what all that overhead is for. The other camp is people mostly working at large corporations, who can't imagine any other way to deal with hundreds of engineers checking in code every day.