Wow. The author is speaking about Javascript front-end frameworks.

I'm an old guy now, and I've rarely seen a need for a front-end framework. I know that sounds like heresy.

I've never bothered to learn Angular, React, NextJS, Svelte or any of the alphabet soup named frameworks. Normal javascript works fine these days for a sprinkling of front-end interactivity. jQuery is not even necessary anymore.

And with more recent technologies like Phoenix LiveView, there is very little need to use any of those front-end frameworks.

Count me as old-fashioned, but very few apps really need those kinds of frameworks. They could mostly do without them.

Frameworks are mostly necessary on the backend.

> Normal javascript works fine these days for a sprinkling of front-end interactivity. jQuery is not even necessary anymore.

If you just need a sprinkling of front-end interactivity, you don't need a framework and you never needed it. If you're building a web application with lots of features, re-used components, complex data structures, etc., a framework helps you a lot. And the web today is full of complex web applications, since most of what used to be desktop applications 15 years ago are now web applications.

That is my application that creates an OS GUI in the browser. Plenty of features with o framework.

* Code size (on the front-end) 2mb unminified.

* Load time in the browser (including state restoration) about 120ms.

* The first version took 15 days to write from scratch.

When people claim there MUST be a framework its clear they have no idea what they are talking about. It is clearly a case of Dunning-Kruger effect where they can compare their experience with frameworks on one hand... and they have nothing to compare it to, because its all they know.