It’s OK to Still Use Angular 1 in 2017
alexkras.com
alexkras.com
I work 2 days a week on maintaining AS3 / Flex projects for around $110/hour, fully remote. Which for my client means a more economical choice than to build a new team and knowledgebase and rewrite.
We also have around 350 different (minor to major) systems running, which won't be upgraded in a foreseeable future.
Using old technology is a consequence of reality, but that doesn't mean it's a good idea. It's very dangerous to get complacent, and I think especially so, with something so replaceable as Angular 1.
The only real business benefit that other frameworks provide is that they make it easier to hire for. If things continue as they have been in a year or two we will have a bunch of new cool frameworks, and current super stars will become old. So why bother switching yet?
For now Angular 1 is not broken (assuming known limitations are OK for businesss need) so why fix it?
That's just us of course.