Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Angular 2.0

blog.angularjs.org

Post reply on HN
Print view View original

1–10 of 169 posts

Re: Angular 2.0

#2

Post by tectonic »

"All code in Angular 2 is already being written in ES6. As ES6 doesn’t run in browsers today, we’re using the Traceur compiler to generate the nice ES5 that runs everywhere. We’re working with the Traceur team to build support for a few extensions like annotations and assertions."

That's pretty cool.

Re: Angular 2.0

#3

Post by opendomain »

Should this be marked as Angular 2.0 BETA? The docs say that it is not done yet.

Also, the docs say that they do not know when they will be done. While I can understand that we may not know problem that arise, it is a pet peeve of mine that I never have a an idea when Drupal 8 will be released. I know that open source contributions are hard to track, we have to estimate (guess) when our projects will be done in our work, so why can we not do it for the projects we love?

Re: Angular 2.0

#4

Post by johne20 »

+1 to "Integration with authentication and authorization". This is needed on 95% of apps or more, nice to know it hopefully will be supported.

oh, and don't forget better documentation :)

Re: Angular 2.0

#5

Post by iSnow »

ES6 support with ES5 fallback, I am stoked.

As to the mobile-first changes, we'll see - I have some reservations on using Angular on lower specced mobiles, for the $watch()-cycle seems to me huge drain on batteries. But since the Angular guys know what they are doing, I am looking forward to nothing but goodness.

Why not just include restangular as one of the resource modules if they decide to go all-out modular?

I am hoping for multiple ngIncludes and a bit easier development of directives, other than that, keep up the good work, guys :)

Re: Angular 2.0

#6

Post by josteink »

tectonic wrote: post #2

"All code in Angular 2 is already being written in ES6. As ES6 doesn’t run in browsers today, we’re using the Traceur compiler to generate the nice ES5 that runs everywhere. We’re working with the Traceur team to build support for a few extensions like annotations and assertions." That's pretty cool.

While "cool" and "clever" and any other half-positive adjective you like, it does mean things will literally be hell to debug until native ES6 support is available in current browsers.

I thought the internals of Angular already had a reputation for being pretty horrible and indecipherable already. I doubt this will improve on any of that criticism.

Re: Angular 2.0

#8

Post by flylib »

opendomain wrote: post #3

Should this be marked as Angular 2.0 BETA? The docs say that it is not done yet. Also, the docs say that they do not know when they will be done. While I can understand that we may not know problem that arise, it is a pet peeve of mine that I never have a an idea when Drupal 8 will be released. I know that open source contributions are hard to track, we have to estimate (guess) when our projects will be done in our w…

looking at the design documents probably a RC in the next 6-8 months

Re: Angular 2.0

#9

Post by rdtsc »

opendomain wrote: post #3

Should this be marked as Angular 2.0 BETA? The docs say that it is not done yet. Also, the docs say that they do not know when they will be done. While I can understand that we may not know problem that arise, it is a pet peeve of mine that I never have a an idea when Drupal 8 will be released. I know that open source contributions are hard to track, we have to estimate (guess) when our projects will be done in our w…

Yeah this a bit is misleading, title gives the impression this is a release announcement, instead it is more of blueprint of "how we plan to do it".

Re: Angular 2.0

#10

Post by chadillac »

josteink wrote: post #6
tectonic wrote: post #2

"All code in Angular 2 is already being written in ES6. As ES6 doesn’t run in browsers today, we’re using the Traceur compiler to generate the nice ES5 that runs everywhere. We’re working with the Traceur team to build support for a few extensions like annotations and assertions." That's pretty cool.

While "cool" and "clever" and any other half-positive adjective you like, it does mean things will literally be hell to debug until native ES6 support is available in current browsers. I thought the internals of Angular already had a reputation for being pretty horrible and indecipherable already. I doubt this will improve on any of that criticism.

That's the reason I've not done anything more than dabble with it. My experiences building anything that wasn't Angular from the foundation up left me frustrated.

This is great for XYZ, but I need to do AB123C... well... shit.

Post reply on HN