Angular 1 and Angular 2 integration: the path to seamless upgrade

Post by NicoJuicy » Wed, Aug 26, 2015, 7:43 PM UTC

jbergens wrote: post #92

NicoJuicy wrote: post #34

Earlier quoted context omitted.

Yeah, it seemed that way because there was no migration path... That is fixed though ;) Almost everyone i know is using something in the likes of AngularJS

> Almost everyone i know is using something in the likes of AngularJS I do wonder what you mean with that. I think that both React and Ember are different but if you mean a javascript framework for building single page applications you're probably right.

Everyone who is following a bit of technology and/or searching for extra developers ( Brussels/Belgium) are all using AngularJS. Haven't found any mention of EmberJS or React or anything ( doesn't mean they don't know it)

There was only one difference, someone used AngularJS with Typescript :) ==> c#

Post by puddums » Wed, Aug 26, 2015, 8:07 PM UTC

tericho wrote: post #43

Seeing a lot of comments about how Angular had no migration plan. Migration was discussed at length at ng-conf back in March, including a large portion of the keynote(s). They made it very clear a smooth and simple migration was top priority. Part of migration talk in keynote: https://youtu.be/QHulaj5ZxbI?t=12m43s Full playlist: https://youtu.be/QHulaj5ZxbI?list=PLOETEcp3DkCoNnlhE-7fovYvq...

Fair point, but worth noting that compared to the migration plan discussed at ng-conf in March, this is now an improved plan. For example, from the post just published:

Wasn't the original upgrade plan to use the new Component Router?

The upgrade plan that we announced at ng-conf 2015 was based on upgrading a whole view at a time and having the Component Router handle communication between the two versions of Angular.

The feedback we received was that while yes, this was incremental, it wasn't incremental enough. We went back and redesigned for the plan as described above.

Re: Angular 1 and Angular 2 integration: the path to seamless upgrade

Re: Angular 1 and Angular 2 integration: the path to seamless upgrade