See , that'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 "Google project" . Everybody knows what other project i'm talking about.
Angular 1 and Angular 2 integration: the path to seamless upgrade
31–40 of 102 posts
Re: Angular 1 and Angular 2 integration: the path to seamless upgrade
#32See , that'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 "Google project" . Everybody knows what other project i'm talking about.
What other project are you talking about?
Re: Angular 1 and Angular 2 integration: the path to seamless upgrade
#33Why isn't there a single domain for the angular project? 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/docs/web/libraries/angular/). Why not have a single site (or at least a main domain with corresponding subdomains) wit…
Re: Angular 1 and Angular 2 integration: the path to seamless upgrade
#34I know that hating angular is popular these days, but i'm still using it, and it serves me well. Looking forward to Angular 2!
Almost everyone i know is using something in the likes of AngularJS
Re: Angular 1 and Angular 2 integration: the path to seamless upgrade
#35Why isn't there a single domain for the angular project? 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/docs/web/libraries/angular/). Why not have a single site (or at least a main domain with corresponding subdomains) wit…
You can try to search using DuckDuckGo as it highlights _official sites_. Really useful feature, even for quick one-time searches.
Re: Angular 1 and Angular 2 integration: the path to seamless upgrade
#36Earlier quoted context omitted.
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.
I'm not sure you are correct. According to the w3 spec for HTML attributes [0], html element attribute names must consist of one or more characters other than the space characters, U+0000 NULL, """, "'", ">", "/", "=", the control characters, and any characters that are not defined by Unicode. Granted, it isn't necessarily what I'd expect to be legal, but it doesn't look illegal either. We may just need to add some l…
Re: Angular 1 and Angular 2 integration: the path to seamless upgrade
#37Earlier quoted context omitted.
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.
BTW, why do I always feel like betting in a horse race when choosing a web framework/library? Hoping it'll be maintained long enough, hoping it'll not be deprecated after 6 months for the new cool kid...
Re: Angular 1 and Angular 2 integration: the path to seamless upgrade
#38"Native mobile UI. We'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."
Re: Angular 1 and Angular 2 integration: the path to seamless upgrade
#39The dramatic shift from version 1 to 2 is generally a sign of design mistakes. Angular 1 should have been angular beta.
Re: Angular 1 and Angular 2 integration: the path to seamless upgrade
#40See , that'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 "Google project" . Everybody knows what other project i'm talking about.