Sharing Top Content from the Angular-sphere.

It’s OK to Still Use Angular 1 in 2017

  • Perhaps choosing Angular 1 is still a valid choice for a large number of companies.
  • It is probably a wrong choice for a brand new company, but for a company that already has a number of Angular projects, I don’t see enough reasons (yet) to choose to support one more framework in addition to Angular 1.
  • There are a number of other completely different frameworks and ecosystems out there (Angular 2+, React, Ember, Aurelia, Vue, Reactive, Mithril, Riot, Elm, Preact, Inferno, Polymer to name a few) and they are all valid choices, if they work for your business and your team.
  • With Angular there are a lot more things decided for you, which could be a very productive benefit for a team already experienced with Angular ecosystem.
  • For a brand new team with no Angular experience, React might be better.

I saw an old friend over the weekend, who is a Director of Front End at a local start up. He asked me what framework we were using, and I said, still Angular 1. He then asked if we used Angular 1 even for the new projects? “Of course not!”, I lied.

I saw an old friend over the weekend, who is a Director of Front End at a local start up. He asked me what framework we were using, and I said, still Angular 1. He then asked if we used Angular 1 even for the new projects? “Of course not!”, I lied.

Later that day it came up that 2 more people were still using Angular 1 at their work. This was very much inline with an informal poll that I conducted earlier, that showed that 64% of developers are still using Angular 1 vs Angular 2+.

This got me thinking, why did I feel the need to lie about our ongoing use of Angular 1? Perhaps choosing Angular 1 is still a valid choice for a large number of companies.

It is probably a wrong choice for a brand new company, but for a company that already has a number of Angular projects, I don’t see enough reasons (yet) to choose to support one more framework in addition to Angular 1.

Angular 1 by now ( mid 2017) has become a boring technology, and as the linked article indicates boring does not mean bad. Angular 1 has a number of shortcomings, but by now they are well understood and addressed.

Angular 1 has a large learning curve, but it also has a great number of resources available to help you get started.

Angular 1 is not very…

It’s OK to Still Use Angular 1 in 2017

Comments are closed, but trackbacks and pingbacks are open.