Why are developers still using this legacy framework?

Nadya Primak - May 25 '19 - - Dev Community

Today I was browsing through my Medium recommendations and came across an article titled "Why are developers still using Angular?"

Check it out here: https://medium.com/@PurpleGreenLemon/why-are-developers-still-using-angular-b9ef29d1f97f

It struck a chord with me, as a developer who has worked for six different companies in my career so far, all of which used Angular. More specifically, the five of the four used AngularJS with the only exception being a very early stage startup where I was able to choose the framework, and went with Angular 6.

While the article focuses on the most recent version of Angular and how it differs dramatically from the original, the author was also quick to condemn AngularJS, hoping it would "die a silent death."

The problem with this attitude, and also the issue I want to discuss, is that many of us are still in jobs where we are using outdated frameworks and technologies. Certainly, we all want to catch up, learn React, learn ES6, Typescript, RxJS, and all the other fun things, but there would literally be no time left in the day and burn out is a serious risk.

So for those of us developers who work in companies that still support or actively program with legacy tech, how do you tackle these problems? Do you just try to get out as quickly as possible? Do you use your precious free time at the end of the day to keep learning the new stuff? Do you just not worry about it, knowing that legacy tech will always be there? I want to hear your thoughts.

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terabox Video Player