Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

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

angularjs.blogspot.com

Post reply on HN
Print view View original

1–10 of 102 posts

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

#2

Post by pfooti »

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.

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.

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

#5

Post by escobar »

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.

Hearing that they are really planning on making it more or less "backwards compatible" is definitely a smart move from the Angular team, and makes me more comfortable potentially suggesting Angular as a framework.

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

#8

Post by ajanuary »

weego wrote: post #3

Remember when we were worried about the semantic purity of our HTML.

I don't know that "semantic" is what you mean here.

Semantics in HTML is about exposing the meaning of content through the DOM. Adding data-binding via attributes doesn't change that at all.

    Name
still encodes just as much semantics as

    Name
I think what you might have meant, as mariusmg mentioned in a sibling comment, is "separation of concerns"? Personally I think that has diminishing returns as your application gets more complex. It's very difficult not to still have tight coupling, just hidden under a layer of indirection.

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

#9

Post by fougerejo »

escobar wrote: post #5

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. Hearing that they are really planning on making it more or less "backwards compatible" is definitely a smart mo…

Since Angular 2 was announced, I had the feeling that I picked the wrong framework for our product with Angular 1, and was feeling regrets about that choice towards my team, to have blocked them with a framework without future.

Knowing that we'll be able to slowly move our app to Angular 2, one feature at a time, is certainly the best news I've had in a while.

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

#10

Post by jrochkind1 »

ajanuary wrote: post #8
weego wrote: post #3

Remember when we were worried about the semantic purity of our HTML.

I don't know that "semantic" is what you mean here. Semantics in HTML is about exposing the meaning of content through the DOM. Adding data-binding via attributes doesn't change that at all. Name still encodes just as much semantics as Name I think what you might have meant, as mariusmg mentioned in a sibling comment, is "separation of concerns"? Personally I think that has diminishing returns as your application get…

I think it's more like "syntactic" then semantic.
Is syntatically valid HTML, although ng-model may not be a legal attribute name in standard HTML. On the other hand:
Isn't even syntactically valid HTML. It kind of rubs me the wrong way too, although I don't know if it matters in practice, although I'm not sure it doesn't either. It does seem ugly.
Post reply on HN