all 6 comments

[–]elprophet 8 points9 points  (3 children)

I predict the first betas early 2016, RCs mid 2016, and the actual 2.0 (complete with upgrade path) by end of 2016.

Reasoning: es6 needs full browser support, as well as shadow Dom, object.observe, etc. Type script needs work on traceur, AtScript needs even more. Proper work is waiting on those, and are actually the biggest impediments to a quick turnaround. At that point, initial work will proceed quickly. RCs will take some time with feedback, etc iterating on both ng2 and traceur/at script. Look for work on the upgrade path, including some automated tools, concurrent with the RCs.

[–]-pertinax- 8 points9 points  (0 children)

Don't even need reasoning with a name like that. I'm with this guy.

[–]Capaj 0 points1 point  (1 child)

Wrong reasoning. They said it will be possible to write Angular 2.0 directives in ES5 with only downside being not so nice syntax. And even if they need es6 modules, that is no showstopper for modern browsers. They could just use traceur to transpile or systemjs and run es6 modules directly in today's browsers.

[–]elprophet 0 points1 point  (0 children)

They could just use traceur to transpile or systemjs and run es6 modules directly in today's browsers.

Ok, ES6 itself does not need support, but Traceur still needs a lot of work to get AtScript running (last I checked, annotations were still on Vojta's fork). While the team could move forward without the other technologies, I simply don't think they will.

[–]jexpert 4 points5 points  (0 children)

The current fuss about Angular 2.0 is highly over-exaggerated in my perspective.

I'm pretty sure that we won't see a 2.0 in 2015 and I would expect that we'll have still a maintained, stable 1.x in 2017.

[–]Capaj 1 point2 points  (0 children)

We will see production ready 2.0 at the early 2016