Four Eras of JavaScript Frameworks (2022)

Quick Cmd-F for "jquery" reveals that it isn't even mentioned as a framework; it lived somewhere in pre-history before the invention of Angular.js. It's terrifying that history "begins" with reliance on anything that abstracts away the separation between JS and the DOM to that extent.

I'm still writing huge apps that take advantage of some easy sugar from Jquery, long after the rise and fall of dozens of frameworks that I never wanted to use. Even after most of Jquery's DOM-searching-manipulation functionality were incorporated into core JS query selectors. (I still use it for one reason: I like having its event loop to hook custom dispatchers and listeners to objects/class instances that don't exist in the DOM; and even though I wrote my own, jquery's is tried and true).

All you need to write a responsive framework is a class that abstracts backend "AJAX" calls, synchronously or not, and manipulates whatever it wants in the DOM with the results. Write your own. Don't rely on it being stuck into junk inside your HTML templates, or you'll never be able to write good large scale applications. I look at my banks' apps (Schwab, Chase) and weep for how awful their coders are and how reliant on those gross frameworks.

Nothing is new. 2022 was a long time ago. I have apps still running from 2012 that look more modern than a lot of new things built with frameworks. I'd never take a job that demanded me to use Vue or Angular or React. Roll your own.