I saw this comment on workspace stackexchange:
I think you are underestimating how much working on legacy stuff can set a developers career back. From the point of view of getting your next job it's basically a gap in your resume at best.
This was controversial, so let's discuss...
Probably, if you want to work on cutting-edge technologies in your next jobs, you should be doing it now. But let's say you mostly care about money (or status or groupies), does it matter if you do Cobol, Java or React?
Do people often totally switch to different stacks in their career?
"Legacy" seems to have such a negative connotation nowadays, but it depends on what they mean by "legacy." To some people, "being stuck" with core tech and vanilla anything is "legacy." In any case, I contend that the strength in your skills and intimate knowledge in handling core tech will go a long way more than the number of "cutting-edge techs" you can list in your resume. Not only that, it will filter out shallow employers/clients, who are too busy chasing after wind to pay more attention to quality and craftsmanship at the foundational level. Good employers worth considering will value your skills in core vanilla tech and other non-tech factors such as knowing how to design things for humans and how you solve various problems. Using a particular tech/tool is just a mean to the end. It doesn't mean you shouldn't learn some of them. I just think that strength in directly handling core/vanilla tech complements you more as an advanced level developer.
Gijo Varghese
A WordPress speed enthusiast
What I've seen is some people run behind the latest cutting-edge technologies like React, Vue etc, but forget to master JavaScript.
Fun fact: GitHub uses uses Vanilla JavaScript, Intercom uses JQuery
PS: Our team switched a from a cutting-edge technology - VueJS to ReactJS!!