3 ms·

Agreed. As great as Angular 2 seems to be, by breaking compatibility to the point they did, they've essentially created another framework. For someone looking

Agreed. As great as Angular 2 seems to be, by breaking compatibility to the point they did, they've essentially created another framework. For someone looking to upgrade from Angular 1.x, this shifts their thought process from "should I upgrade to Angular 2?" to "which new framework should I upgrade to?". And for many people, that new framework isn't going to be Angular 2.

mmastrac 11y ago
As someone who loves Angular, searching for information on Angular 1 vs Angular 2 is insanely frustrating. They should have just renamed the damn thing.
johnatwork 11y ago
It's actually why my company ditched Angular. Even though the Angular part wasn't very big at the time and the rewrite would not have been too costly, it would not have been wise to move to Angular 2 just to have them pull the same thing again for Angular 3.
Bahamut 11y ago
The Angular team is currently exploring options to ease the upgrade path - the current plan last I saw is to create an engine that runs angular 2 components in angular 1 and vice versa for seamless interop, so upgrading can be more incremental. That is an evolving story, which has changed several times before reaching that point. That said, Angular 2's performance is already looking phenomenal, and assuming some of the stats I have seen out in the wild are to be believed, it can run over 30x as fast as some of the existing frameworks for large datasets, including angular 1. If I had to choose a library to use now, it'd be React, but if I had the opportunity to hold off upgrading, I would absolutely wait for Angular 2.
couchand 11y ago
There's a very natural upgrade path from Angular 1.x to React: start building new little components in React and patch them into your app in Angular directives. You can even apply the flux pattern to good effect within the directive while still making use of your existing Angular service infrastructure. Per Evans this would be an Evolving Order over a pair of Bounded Contexts.

mmastrac 11y ago

As someone who loves Angular, searching for information on Angular 1 vs Angular 2 is insanely frustrating. They should have just renamed the damn thing.

johnatwork 11y ago

It's actually why my company ditched Angular. Even though the Angular part wasn't very big at the time and the rewrite would not have been too costly, it would not have been wise to move to Angular 2 just to have them pull the same thing again for Angular 3.

Bahamut 11y ago

The Angular team is currently exploring options to ease the upgrade path - the current plan last I saw is to create an engine that runs angular 2 components in angular 1 and vice versa for seamless interop, so upgrading can be more incremental. That is an evolving story, which has changed several times before reaching that point. That said, Angular 2's performance is already looking phenomenal, and assuming some of the stats I have seen out in the wild are to be believed, it can run over 30x as fast as some of the existing frameworks for large datasets, including angular 1. If I had to choose a library to use now, it'd be React, but if I had the opportunity to hold off upgrading, I would absolutely wait for Angular 2.

couchand 11y ago

There's a very natural upgrade path from Angular 1.x to React: start building new little components in React and patch them into your app in Angular directives. You can even apply the flux pattern to good effect within the directive while still making use of your existing Angular service infrastructure. Per Evans this would be an Evolving Order over a pair of Bounded Contexts.