News for hackers. Stuff that matters.
Re:AngularJS: The Bad Parts by ddoolin on Wednesday November 05, 2014 @12:44PM (#8563037)
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

Re:AngularJS: The Bad Parts by michaelchisari on Wednesday November 05, 2014 @12:47PM (#8563062)
The addition of a whole new scripting language seems... overly complicated.
Re:AngularJS: The Bad Parts by paulhodge on Wednesday November 05, 2014 @01:06PM (#8563185)
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.

Re:AngularJS: The Bad Parts by emilis_info on Thursday November 06, 2014 @05:09AM (#8566429)
I think it is more Dart... At least the AtScript specification mentions Dart more often than any other language.
Re:AngularJS: The Bad Parts by alexsopilot on Wednesday November 05, 2014 @01:52PM (#8563483)
The language is layered on top of Javascript and is completely optional.
Re:AngularJS: The Bad Parts by EugeneOZ on Wednesday November 05, 2014 @03:58PM (#8564210)
It's not new language, just syntax sugar. And optional.
Re:AngularJS: The Bad Parts by kuni-toko-tachi on Wednesday November 05, 2014 @01:06PM (#8563190)
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.
Re:AngularJS: The Bad Parts by mcv on Friday November 07, 2014 @06:28AM (#8572034)
What?! I finally understand all the aspects of the directive definition object, and now they're throwing it out?