What a fantastic set of responses! And no, this article is not "click bait".

What we're seeing here is indeed a kind of perspective issue between younger and more seasoned engineers who have been using JS for decades instead of just years.

It's not a matter of "keeping up with the times" or keeping one's skills sharp, it's a matter of not adopting every fad technology that comes down the pipe. Especially within the enterprise environment.

Most people have never even heard of YUI, but that was the precursor to all of these other frameworks that are popular now. And where is YUI today? Gone. Replaced with the next flavor of the day.

Using JS libraries are fine. We all use them. But it's when the whole application depends on some continually updating "framework" that now becomes yet another dependency or has reliance of even more dependencies within the code or CI/CD pipeline that the whole thing starts to become a mess.

This is not organized code, it's a mess. If we need highly opinionated frameworks to teach us how to organize and write proper code, we're not being taught to code properly.

Likewise, if I have to install Node.js, et. al., to run something locally or build it in the pipeline, it doesn't get used. That's not being "old school", nor does it have anything to do with keeping one's skills up to date with the latest fad tech. It's merely intelligent engineering.

Great perspectives, everyone. I love what the comments are illustrating!