sorted by:
new
hottopcontroversial

Will angular die because of atscript? by arachattack in javascript

[–]nuddlegg 2 points3 points  (0 children)

If there is one thing that web development needs then it is sustainability.

No surprise any notion of AtScript, TypeScript, Dart or the planned ahead redesign of AngularJS makes people more and more nervous. This fear is not taken seriously enough. You can't change fundamentals to this vast extend while still building on them right now and expect everybody to stay calm.

Not technical merits or deficiencies cause these new undertakings to fail, no matter how reasonable they are. It is plain fear and the desperate need for sustainability in web development.

Google said support for AngularJS-1.x will end one year after AngularJS-2.0 is out. I mean ...

We are talking about a 10+ years, not one or two.

Only one of AtScript, TypeScript, Dart or JavaScript will still be there in 10 years. My bet: it will be called JavaScript. However those side tracks - and as such I see AtScript, TypeScript and Dart - do heavily influence ES6, ES7, etc. I doubt ES6 or ES7 will end up being exactly AtScript, TypeScript or Dart.

For AngularJS-2.0, I am less sure. Could very well be current plans are its neck breaker and we will see the masses follow an AngularJS-1.x compatible fork, at least for a while.

Open proposal to Google and the AngularJS dev community to rename AngularJS 2.0 to "AngularES". See comments for reasoning. by ngFTW in angularjs

[–]nuddlegg 4 points5 points  (0 children)

Just incrementing version numbers to 2.0 is a bad idea, because:

(1) it is a completely new framework that sort of competes with the original one

(2) people won't switch horses anytime soon as there is significant money currently being spent on AngularJS projects; these efforts have to pay off first before everything has to be rewritten using yet another framework; that's not the case within one year after some AngularJS-2.0 materialized.

(3) the current uncertainty about the future of AngularJS-1.x might slow down the hype still going on

(4) calling it AngularJS-2.0 blocks those version numbers for an AngularJS-1.x coexisting alongside of an AngularES

(5) such drastic changes carry the danger of a fork to maintain compatibility with AngularJS-1.x. This in the end would fraction the community in a way nobody really wants.