Live data from Hacker News

Angular 2.0 Website

angular.io

1–10 of 47 posts

Re: Angular 2.0 Website

#3
their about page is broken, cutting off text of the bio at almost all screen sizes.

there is a weird "rawgit traffic error" banner across the site.

Re: Angular 2.0 Website

#5
> Angular 2 is currently in Alpha Preview. We recommend using Angular 1.X for production applications.

Not sure how they can "recommend" 1.X when it's completely incompatible with 2.0. Might as well recommend Ember, React, or literally anything else.

Re: Angular 2.0 Website

#7

> Angular 2 is currently in Alpha Preview. We recommend using Angular 1.X for production applications. Not sure how they can "recommend" 1.X when it's completely incompatible with 2.0. Might as well recommend Ember, React, or literally anything else.

Why would they recommend something other than angular on the angular homepage?

Re: Angular 2.0 Website

#8

> Angular 2 is currently in Alpha Preview. We recommend using Angular 1.X for production applications. Not sure how they can "recommend" 1.X when it's completely incompatible with 2.0. Might as well recommend Ember, React, or literally anything else.

At ng-conf in the opening remarks they talked about how they plan to have people migrate from 1.X to 2.0. From what I understand if you start using the new router in Angular 1.4 then that will be the router for 2.0 which will allow you to use Angular 2.0 with 1.X components as you slowly migrate each 1.X component to 2.0. I think this is pretty reasonable.

Re: Angular 2.0 Website

#9
post #7

> Angular 2 is currently in Alpha Preview. We recommend using Angular 1.X for production applications. Not sure how they can "recommend" 1.X when it's completely incompatible with 2.0. Might as well recommend Ember, React, or literally anything else.

Why would they recommend something other than angular on the angular homepage?

[deleted]

Re: Angular 2.0 Website

#10

> Angular 2 is currently in Alpha Preview. We recommend using Angular 1.X for production applications. Not sure how they can "recommend" 1.X when it's completely incompatible with 2.0. Might as well recommend Ember, React, or literally anything else.

> Not sure how they can "recommend" 1.X when it's completely incompatible with 2.0

I'm tired of people saying this. It's simply not true. The core team has said multiple times that there will be a migration path and they just announced today that you will be able to mix v1 and v2 components within the same project.

Post reply on HN