jQuery is great at generating tech debt. It can also do DOM binding. Any attempts to organize and make sense of someone's unstructured jQuery code will result

jQuery is great at generating tech debt. It can also do DOM binding. Any attempts to organize and make sense of someone's unstructured jQuery code will result in an ad hoc "hot-rodding, fly-by-the-seat-of-my-pants" framework that only the guy(s) who originally wrote it know(s). That won't fly in the "enterprise world". Also, I'm not an Angular guy (I actively refuse to work with it), but to lambast Angular 2+ for its version numbering -- which I think is just semver?, and give React a pass for the same thing (hey guess what, React is at v17 now) is odd to me. By dismissing TypeScript on principle, this guy is losing out immensely (hey guess what #2, if you're using Gulp or Grunt (uh, in 2021?) which the author says he's OK with, it's a 10 minute job to add a TS or Sass compilation step)). Unless you only use that for production builds, I suppose. But if so, does that mean the author maintains an ordered list of JavaScript/CSS files to import during dev time? Oh. Oh no. That won't save you any time. If you're that afraid of learning new things, maybe just frontend isn't for you. And that's OK. But maybe don't be so proud of it.