3 ms·

Yes both are ways to deal with single page applications... 2 way data-binding is still in Angular2, as well as oneWay Binding to the input and one way binding

Yes both are ways to deal with single page applications... 2 way data-binding is still in Angular2, as well as oneWay Binding to the input and one way binding from output. I've heard others make the claim ng-model and 2 way binding are gone, which is wrong. https://egghead.io/lessons/angular-2-using-ng-model-for-two-way-binding https://egghead.io/lessons/angular-2-using-ng-model-for-two-... There are giant performance benefits on the horizon with Angular2 in terms of server side rendering with Angular Universal and state management with ngrx/store. In Angular2 http is handled as an observable, no longer a promise, so there is a difference in syntax but that falls in line with ES7 format

Roboprog 11y ago
Thanks for the update. As far as I could piece together (admittedly dubious connections), ngModel was re-implemented in the Jan 2016 release of Angular 2??? ("Angular 2.0.1 beta" from a Stack Overflow discussion assumed to mean 2.0.0-beta.1 on https://code.angularjs.org/ https://code.angularjs.org/) Sounds like somebody beat some sense into the Angular 2 team - "don't remove the single feature that differentiates your library and makes prototyping an app easy" Now if I can only find examples in good old Javascript, instead of fugly, Java-esque, Typescript. Re: types/Typescript - loved this quote: "Better type-checks interestingly found only just a few bugs" https://jaxenter.com/angularjs-interview-angular-2-typescript-and-a-release-date-123674.html https://jaxenter.com/angularjs-interview-angular-2-typescrip... Rant for another day: insisting on static typing, but ignoring the mayhem caused by operators and operator precedence (to say nothing of user created operators)