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

I have been evaluating writing some new applications in Angular at work and was quickly turned away from it because before today the actual migration path seemed very unclear. Without a migration path, picking v1 for a new application at this point would be silly, and 2 is completely unready for production.<p>Hearing that they are really planning on making it more or less &quot;backwards compatible&quot; is definitely a smart move from the Angular team, and makes me more comfortable potentially suggesting Angular as a framework.

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.<p>Part of migration talk in keynote: <a href="https:&#x2F;&#x2F;youtu.be&#x2F;QHulaj5ZxbI?t=12m43s" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;QHulaj5ZxbI?t=12m43s</a><p>Full playlist: <a href="https:&#x2F;&#x2F;youtu.be&#x2F;QHulaj5ZxbI?list=PLOETEcp3DkCoNnlhE-7fovYvqwVPrRiY7" rel="nofollow">https:&#x2F;&#x2F;youtu.be&#x2F;QHulaj5ZxbI?list=PLOETEcp3DkCoNnlhE-7fovYvq...</a>

I know that hating angular is popular these days, but i&#x27;m still using it, and it serves me well. Looking forward to Angular 2!

This looks nice. I like the idea of more-or-less seamless integration between a1 and a2 on the same page, to allow for incrementally experimenting with a2 features without having to port the entire application over.<p>With angular 2 moving to a virtualdom implementation we can get serverside rendering and some real speed improvements (if you move your virtualdom stuff to a web worker for example). This is rad.

Every time I use Angular it feels like it&#x27;s doing things the right way and it&#x27;s becoming the Rails or Django of the JavaScript world. Wish I had fought to use AngularJs directives and $resource instead of messing about with ReactJS and jQuery ajax calls.<p>With this migration plan it seems silly <i>not</i> to keep hacking with AngularJS 1.x

I see 2-way data-binding is mentioned here and will still be supported (good). Curious why has 2-way now become &#x27;uncool&#x27; recently, e.g. React? 2-way is what got me excited about client side JS due to the code reduction in an average app. Is just that Angular 1&#x27;s implementation was non-performant? (lots of other frameworks use it as well, e.g. Knockout, RactiveJS, etc).

Why isn&#x27;t there a single domain for the angular project?<p>From what I can see there seems to be 2 main ones: angular.io (for angular 2) and angularjs.org (for angular 1.x) as well as angulardart.org and other sites for angular material design (material.angularjs.org) and angular firebase (firebase.com&#x2F;docs&#x2F;web&#x2F;libraries&#x2F;angular&#x2F;). Why not have a single site (or at least a main domain with corresponding subdomains) with similar documentation and navigation?<p>In addition, searching for &quot;angular&quot; in Google provides no obvious distinction between the different sites. For a Google sponsored project, I would have expected better attention to the search meta-data to make the distinction clear.

See , that&#x27;s how you manage an open source project , you listen to your community , and yes people can have relevant suggestions. Angular JS became successful because of its pragmatism but also because it allowed more than 1000 people to contribute to its core, not because it was a &quot;Google project&quot; .<p>Everybody knows what other project i&#x27;m talking about.

&lt;input type=&quot;text&quot; [(ng-model)]=&quot;model.name&quot;&gt;<p>Remember when we were worried about the semantic purity of our HTML.

&gt; We&#x27;ve decoupled Angular 2&#x27;s rendering from the DOM.<p>Does this mean they are using some sort of virtual dom a la React?

if I&#x27;m reading this correctly, they also planning to release a react native competitor?<p>&quot;Native mobile UI. We&#x27;re enthusiastic about supporting the Web Platform in mobile apps. At the same time, some teams want to deliver fully native UIs on their iOS and Android mobile apps.&quot;

One of the biggest benefit of Angular is the vast amount of libraries built on it, like bootstrap-ui and ui-grid to name a few, how can we switch to Angular 2 until the most adopted ones don&#x27;t switch too? (real question)

Commets here made me think about whether it&#x27;s forward-looking using angular 1.0 for next projects: i guess i&#x27;ll go with React with my short-coming project then... I don&#x27;t know what to do

Anyone knows how Angular 2 plays with &quot;outside&quot; code? It is very frustrating, having to convert everything to a directive when using with Angular 1.

For the curious, this is the official repository for the ng2-to-ng1 engine: <a href="https:&#x2F;&#x2F;github.com&#x2F;ngUpgraders&#x2F;ng-forward" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;ngUpgraders&#x2F;ng-forward</a>

This is really great news for my company, as we have several Angular 1 applications still in development that can benefit from this incremental upgrade pattern.

Finally! There has been talk for what seems months for an upgrade path. I&#x27;m so happy that there is finally some clarification.

The dramatic shift from version 1 to 2 is generally a sign of design mistakes. Angular 1 should have been angular beta.

Slightly off topic, sorry, but I do HATE how blogger.com sites are totally unusable with JS turned off &#x2F; noscript &#x2F; etc ...

Aurelia is looking nice right now.