Re:Angular 2 Release Candidate
by craigvn on Tuesday May 03, 2016 @01:44AM
(#11618216)
It is the million dollar question. If you are building a large product with an expected life of 10+ years, can you trust Angular to still be maintained?
[ Parent
| on HN ]
Re:Angular 2 Release Candidate
by randiantech on Tuesday May 03, 2016 @02:13AM
(#11618322)
I cant recall a single UI library / framework (with the solely exception of Jquery) to be mantained that much. In less than 5 years VR, AR will probably be mainstream, and UI technologies will probably to be revisited from ground up again.
Can you trust the web as we know it to exist in 10+ years?
short answer: "No".
Explanation: In js land, Long term Support means "6 months". so your best bet is to have a framework which makes migrations easy and does not introduce changes.
With angular being backed by google, there is no guarantee if angular will be maintained 4 years down the line.
PS: feel free to keep your million dollar.
> With angular being backed by google, there is
> no guarantee if angular will be maintained 4 years
> down the line.
It's interesting to see that the reason why many companies choose Angular (Google backs it) now seems one of it's biggest disadvantages.
Re:Angular 2 Release Candidate
by robwormald on Tuesday May 03, 2016 @03:46AM
(#11618690)
Angular 1.x has been around since 2009 - 7 years - that predates pretty much every framework in use today, before modules (commonJS, let alone ES6) were widely in use, etc. At some point, we had to make a decision to be forward looking towards the future of the language. Support for 1.x won't disappear for some time. Angular 1.5 had a number of big upgrades - a focus will be easing the transition to 2.x over time ( .component(), lifecycle hooks, etc...)
You're about 3 years out I'm afraid: https://github.com/angular/angular.js/releases/tag/v1.0.0
Even the earliest pre 1.0 releases of Angular weren't until late 2010.
I think there is another problem. With framework the size of of angular is hard to maintain. It will be hard for others to take over if needed. With react's smaller parts every part (redux, react-router, etc) can be maintained by a small group of people. If some part isn't maintained anymore you can switch out that part. With angular you might have to rewrite the whole application. That is a risk I would like to avoid.