This is framework fatigue. Ruby on Rails for example made, and still makes, front and back end web development tenable for people who don't necessarily know wha

This is framework fatigue. Ruby on Rails for example made, and still makes, front and back end web development tenable for people who don't necessarily know what happens behind the scenes. The same goes for Angular in the front end. When you're starting out your programming career by programming against a framework, you'll get very very good at doing things within that framework. However, in the absence of exposure to lower levels of abstraction, this knowledge will be your glass ceiling. There comes a time when you need to level up as a developer - this usually means getting a deeper understanding of what it is you actually do. Of course, we're all web framework developers in a sense, even people who tend to roll their own HTML/JS/CSS - and even these require you to look deeper into how browsers perform tasks - but higher level frameworks tend to obscure things quite a bit more. Also, higher level frameworks tend to have high rates of internal change and external churn. To make matters worse, a lack of more fundamental knowledge will always mean you're at a severe disadvantage when judging the benefits and drawbacks of new frameworks as they come out. A fad-based choice of programming tools is not a good recipe for keeping your sanity, because you're perpetually reacting to any whim happening on the cutting edge, especially if you follow the exaggerated bi-annual trends slavishly ("and now, EVERYTHING has to be done in React!") - on the other hand having an ear on the ground will help you. Fads do serve a purpose, because they expose you to new ideas. But they kill you just as quickly if you pivot your entire professional life to accommodate them.