Angular 2.0 Website • Hacker News Board

Re: Angular 2.0 Website

#11

Post by [deleted] » Thu, Mar 05, 2015, 5:12 PM UTC

ibero wrote: post #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.

[deleted]

Re: Angular 2.0 Website

#12

Post by mooredinty » Thu, Mar 05, 2015, 5:13 PM UTC

Angular is the new PHP... Queue the haters

Re: Angular 2.0 Website

#13

Post by raju » Thu, Mar 05, 2015, 5:16 PM UTC

I am confused seeing this - This mentions "ES6, AtScript, and the es6-shim" ... but the other story on HN speaks about "Angular2 in TypeScript" [http://blogs.msdn.com/b/typescript/archive/2015/03/05/angula...]

What am I missing here?

Re: Angular 2.0 Website

#14

Post by andrewstuart2 » Thu, Mar 05, 2015, 5:19 PM UTC

raju wrote: post #13

I am confused seeing this - This mentions "ES6, AtScript, and the es6-shim" ... but the other story on HN speaks about "Angular2 in TypeScript" [ http://blogs.msdn.com/b/typescript/archive/2015/03/05/angula... ] What am I missing here?

IIRC, AtScript is a superset of both ES6 and TypeScript.

Re: Angular 2.0 Website

#15

Post by codebeaker » Thu, Mar 05, 2015, 5:20 PM UTC

Interesting to see here that the docs still refer to AtScript, where there's an announcement from Microsoft on the homepage explaining that Angular2.0 will use Typescript.

Re: Angular 2.0 Website

#16

Post by mooredinty » Thu, Mar 05, 2015, 5:20 PM UTC

raju wrote: post #13

I am confused seeing this - This mentions "ES6, AtScript, and the es6-shim" ... but the other story on HN speaks about "Angular2 in TypeScript" [ http://blogs.msdn.com/b/typescript/archive/2015/03/05/angula... ] What am I missing here?

They announced today that they're retiring the AtScript name and using TypeScript going forward. The new version of TypeScript is a combination of the old TypeScript and AtScript.

Re: Angular 2.0 Website

#17

Post by 100k » Thu, Mar 05, 2015, 5:21 PM UTC

mooredinty wrote: post #12

Angular is the new PHP... Queue the haters

I think the idiom is "Cue the haters" but "queue the haters" does have a nice image to it. I'm imagining a long line of haters waiting patiently to dis Angular.

Re: Angular 2.0 Website

#18

Post by andrewstuart2 » Thu, Mar 05, 2015, 5:22 PM UTC

woah wrote: post #6

rdsubhas wrote: post #2

And all hell breaks loose again in the JavaScript world.

The original angular seemed to mostly be advocated for by people new to JavaScript.

Being new means you're less likely to be tied down by old assumptions and sunk costs as you evaluate the available tools for your use cases.

Re: Angular 2.0 Website

#19

Post by dmarg » Thu, Mar 05, 2015, 5:23 PM UTC

mooredinty wrote: post #10

martingordon wrote: post #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.

> 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.

I agree with you completely. People just want to complain.

Re: Angular 2.0 Website

#20

Post by mooredinty » Thu, Mar 05, 2015, 5:27 PM UTC

mooredinty wrote: post #10

martingordon wrote: post #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.

> 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.

In addition to allowing your app to share components, they are also back porting parts of v2 to v1. So far, the router and ng-animate and I'm sure more will come.