5 ms·
Angular 2 came out in 2016. Why use angular 1 in 2017?
by davidjnelson 8y ago
Angular 2 came out in 2016. Why use angular 1 in 2017?
- krzyk 8y agoLegacy project? Migrating from AngularJS to Angular >= 2.x is not that easy if you build a framework arond AngularJS. E.g. in my company we use AngularJS because of that.
- xab9 8y agoYou probably are not aware how many (rather big) projects out there are still on angular 1 with no upgrade plan at all. Last time I turned down a job offer because of a similar scenario.
- BillFranklin 8y agoHi, xab9. Out of interest, why did you turn down a job because they are working with a framework version from 2016?
- xab9 8y agoThis was A1, which came out in 2010. I've spent two years using it, I know its strengths and weaknesses, there are just better offers out there.
- megaman22 8y agoIt was 2016 when we started this front-end rewrite, away from a mess of jQuery and Razor view spaghetti. Angular 2 was brand new, without much support for third-party components we used, and AngularJS looked like the mature option. Probably should have bet the other horse, but c'est la vie.
- aeriklawson 8y agoWe're in the middle of upgrading from Angular 1 to Angular 5 (probably now 6) - it's not that hard and I'd recommend doing it.
- vonseel 8y ago4 major version bumps in 2 years!!