> I concern myself with fundamentals, not framework-flavor-of-the-month. The whole framework-of-the-month thing is a meme. The overwhelming majority of compani

> I concern myself with fundamentals, not framework-flavor-of-the-month. The whole framework-of-the-month thing is a meme. The overwhelming majority of companies use Angular, React or (to a lesser extent, Vue). There hasn't been a serious new framework in years, except maybe Svelte, which hasn't really caught on. > What I am not comfortable with is the stubbornly-held strong opinions many JS devs have. Much of the time, a particular JS dev will believe their way is the one-true-way(tm) (which is a problem among a lot technologists in general). so...not actually a problem with JavaScript if it's a problem among "technologists in general" > I get bent when JS devs judge me for not staying up to date - JS is my 9 to 5, not my life. I'm a professional JS dev too. I don't study it on my own time, but reserve a portion of my work time for keeping up to date with language changes. Maybe nobody is paying you to do that explicitly, but having a modern JS vocabulary could mean the difference between getting the next job or not, or how much you get paid. when I got hired at my current job it took me 2 days to start being productive because they were writing modern React and I was used to the current paradigms. I'm so tired of devs online ranting about how the problem with JS is that everybody expects them to keep learning new things. Do what you want, but keep that "JS devs are the problem" stuff to yourself. Maybe you'd be happier writing BASIC with GOTOs