> I've seen people, lead and principal engineers, who refuse to learn modern JS, insisting that since it was bad in 2006 it's bad today. Worse still is some of these people have used their leadership positions to prevent the use of modern JS, of component frameworks like react/vue, from being used across an organization.
Hold on... this is an incomplete thought. What did they say to do instead?
I'm serious. Did they built a pretty good system with Ruby on Rails, Java, or Laravel instead? Did they just use stock JavaScript without a framework? There are perfectly legitimate reasons why a developer might say that, for a certain organization, React is completely unnecessary and a symptom of overengineering. Also, for the few people writing new web apps in 2023 that don't require JavaScript, good for them.
In that particular case, we were made to stick with a hodgepodge of homemade components, server-side template includes, jQuery, and a couple of third-party libraries like select2.
Hold on... this is an incomplete thought. What did they say to do instead?
I'm serious. Did they built a pretty good system with Ruby on Rails, Java, or Laravel instead? Did they just use stock JavaScript without a framework? There are perfectly legitimate reasons why a developer might say that, for a certain organization, React is completely unnecessary and a symptom of overengineering. Also, for the few people writing new web apps in 2023 that don't require JavaScript, good for them.