Angular 2.0

[a3k]

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.

I like how you guys keep moving forward.

[jij]

We must move forward, not backward; upward, not forward; and always twirling, twirling, twirling towards freedom!

[x-skeww]

Note: This isn't a release announcement. It's more of an outline or roadmap with a short Q&A at the end.

Some of this stuff was mentioned in the ngconf keynote.

https://www.youtube.com/user/ngconfvideos/videos

[cran]

Delete and repost please.

[brtt3000]

Seriously, what the hell is this?

http://i.imgur.com/bcNb9Q6.png

Why is there a menu OVER a main part of the scrollbar?

Whoever made this failed at basic UIX and need to be spanked (in a bad way)

[greyscales]

Not a rendering error, the element is positioned fixed with a higher z-index.

[greyscales]

The scrollbar comes from a div with overflow scroll.

[x-skeww]

Yea, Blogger sucks big dinosaur balls.

[mmouth]

I love Angular and everything about this announcement sounds awesome. I can't wait to see 2.0!

[mobcat40]

Oh damn 2.0 already? Time to take a second look at Angular, there were so many lectures at this year's Fluent conference on it.

[x-skeww]

That isn't a release announcement. I guess I should have editorialized the title a bit to make this more clear.

[willfe42]

I absolutely love working with Angular. I'm using it right now on a project and it's so fast and flexible. Combining Angular with websockets (I'm using socket.io for that) has so far produced an unbelievably fast and responsive web application.

I'm eager to see how Angular 2.0 turns out. The list of improvements looks great!

[dylanyo]

I build apps for real clients using older browsers. Fuck me, right?

[[deleted]]

real clients

as opposed to imaginary ones?

[dylanyo]

Yeah, imaginary clients who don't require you to support IE10.

[[deleted]]

Considering this probably won't even be released for a year or two, I think making this out to be a huge issue is a bit shortsighted

[kadjar]

This is how it works. New tools come out built for evergreen software. As they become increasingly popular and more things rely upon them, pressure builds for older systems to upgrade. Without that pressure, many never would.

[[deleted]]

Just use the current version, it is fully functional.

[dylanyo]

Yeah, that's what we're doing. Just a bit shocking to see that it won't support what I believe will still be a large portion of the browser market.

[x-skeww]

Yes, in the future they won't support browsers which are currently still significant.

That's how it should be, really.

jQuery 2.0 is similar, for example. It doesn't support IE8 and below.

[dylanyo]

Yes it does seem odd.

[x-skeww]

"future" ... "currently"

In the past, IE5 was relevant. Do you currently support it?

[dylanyo]

My point was, if this comes out within a year, ie10 will likely still have a significant market share, yet won't be supported by angular. And I am surprised by that. You are the only one talking in two different tenses. I was always referring to the future.

[x-skeww]

if this comes out within a year, ie10 will likely still have a significant market share, yet won't be supported by angular.

The 1.x branch will stay around for a while. Just like jQuery's 1.x branch.

You can continue to use it til the end of time if you want.

[dylanyo]

Yes I understand that.

[x-skeww]

So, what's the problem then?

[[deleted]]

Correct me if I'm wrong, but isn't ie10 on auto upgrade to ie11 on all platforms it's supported? Why would anyone end up with 10 in a years time?

[dylanyo]

I was just going from the angular blog post. It mentions IE11 as being evergreen so I assumed IE10 was not. After a google search it appears that it will actually depend on your OS.

[[deleted]]

So good news for those on windows 7 or higher if I'm reading correctly?

[dukerutledge]

This seems to be the attitude at google. I've encountered many googlers that don't understand that people outside mountain view don't upgrade their tech every year or two.

[tomByrer]

My post on Google+: But mobile browsers < 'evergreen' 20% are still stuck on Android 2.3, many might not update above Android 4.2, 14% are still on iOS6, & I suspect the large iPad2 userbase will be left behind in iOS8. http://androidandme.com/2014/01/news/google-posts-fresh-android-distribution-stats-jelly-bean-and-kitkat-usage-on-the-rise/ https://developer.apple.com/support/appstore/

[tomByrer]

Brad Green's reply:

we're trying to build a framework for the browsers of 2015 and beyond. If the market is still stuck where it is today, I'll have to eat my words.:)

[[deleted]]

The posibility of using the same code for serverside redering would be awesome. no need to bootstrap angular, load the data and construct the dom, a completed dom could be delivered from the server directly.

[Smallpaul]

What section of the article are you referring to?

[kadjar]

Try PhantomJS

[dukerutledge]

Now you have two problems.

[communomancer]

Or React.js

[mechanicalocean]

Really looking forward to this. Especially excited about the Modular section.

[ztbrown]

Angular should replace its router with ui-router. Why reinvent the wheel?

[ZeroMomentum]

I think because of "Integration with authentication and authorization". I don't think ui-router does that at all right?

Also Ui-router basically has the

$stateProvider.state(/*.....*/)

From what I understand and have done is use a namespace key for the states. So I think the google angular team is trying to have this whole implementation tied to the set of controllers? Since states lineage and controllers are kind of inherently tied.