From http://jaxenter.com/angular-2-0-112094.html http://jaxenter.com/angular-2-0-112094.html: > the framework will be “drastically different looking”, meaning

From http://jaxenter.com/angular-2-0-112094.html http://jaxenter.com/angular-2-0-112094.html: > the framework will be “drastically different looking”, meaning users will need to get to grips with a new kind of architecture. It’s also been confirmed that there will be no migration path from Angular 1.X to 2.0. > Currently Angular is aiming for a release by the end of 2015 – but early 2016 seems more realistic given the drastic changes that are planned. This essentially makes investing in Angular pointless, when there are far more capable and easier to learn frameworks out there - Meteor primarily, and also Derby.js, though it's got about 1/10th of the momentum of Meteor, which launched 1.0 two days ago, and had 20k GitHub stars without backing from some giant company. BTW, Meteor never broke compatibility with earlier releases in such drastic ways as Angular will.