Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

that's why 2.0 is complete rewrite - exactly to eliminate all these bad parts.


And to make up for it, they threw in some even worse parts. Like breaking the syntax of HTML with their templates, making it impossible to edit, validate, transform, generate or consume templates with any of the thousands of existing HTML and XML processing tools.

That, in my opinion, was one of the most terrible ideas I've ever heard come out of the Angular community. And even worse, they refuse to acknowledge that it's a bad idea. That's a very bad sign indeed.


They moved away from that idea: https://github.com/angular/angular/issues/133


Can you specify some of the forthcoming improvements? I want to like Angular, but every time I've actually used it has been a practical and conceptual headache. (Also, the idea that they're creating a new compile-to-JS language seems strange and unnecessary.)


A decent overview: http://www.infoq.com/news/2014/10/angular-2-atscript

The kicker is elimination of these concepts: Controllers, Directive Definition Object, $scope, angular.module, and jqLite


The addition of a whole new scripting language seems... overly complicated.


It's TypeScript with the addition of a few key features that are helpful for Angular's design.

Technically, Angular 1.0 also had its own scripting language too. It's kind of inevitable, since Javascript itself is one of the obstacles to making a better web framework.


I think it is more Dart... At least the AtScript specification mentions Dart more often than any other language.


The language is layered on top of Javascript and is completely optional.


It's not new language, just syntax sugar. And optional.


It's utterly insane. Just as in AngularJS 1.3 they have invented there own expression language which floats around in HTML attributes, thereby eliminating the use of Javascript itself and all it's functional goodness. And worst, the user has to incur the cost of downloading this needless code for the expression language to bootstrap the framework.


What?! I finally understand all the aspects of the directive definition object, and now they're throwing it out?


Check out examples of using TypeScript with Angular (or DartAngular). Gives you a lot of benefits today. Personally I think Angular is great but React is even better and I will probably use the latter for my next project if I can choose.


Does it eliminate 2-way data binding?

It's the realisation that this is a fundamentally bad idea that was the real kicker for me.

The more you try to write clearly structured, maintainable Angular, the more it begins to resemble React.



default binding planned to be one-way.


Because "let's rewrite it all from scratch!" always ends well.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: