> I am however feeling so overexposed to new libraries and frameworks that I can hardly muster the energy to even look at it.
That's the nature of the job. In the front-end new frameworks are born all the time, new apis are created, new paradigms are "invented". Coming up with the "perfect" framework is clearly a work in progress.
Here is a list of the techs I had to learn and work with during my career :
- flex
- jquery
- extjs
- backbonejs
- angularjs 1.x
- Reactjs
- angularjs 2.X
And i'm only talking about "view frameworks" here. Not even about the crazy js pipelines involving build tools, running on nodejs , 3 different CSS pre- processors , ...
And in 1 year i'm pretty sure i'll have to work with yet another new framework because managers think framework Z isn't cool enough anymore.
Again that's the nature of the job,because front-end techs are evolving. Everybody was praising backbone 3/4 years ago. Then everybody was praising Angular then everybody is praising React as the new hot stuff.
In the front end, either you keep on learning new stuff, or you're out of job.
Those who believe they have "job security"(as I read in this thread) because they chose angular are lying to them self.
Being a front-end developer means having to learn a shit tons of libraries , techs and apis everyday. You can't just tell yourself , "I'll learn X and i'll be all set" like with server-side techs.
Yet today the biggest challenge isn't even choosing a framework, but more like choosing how to transition from ES5 to ES6. Because the tools aren't ready.