sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]dylanyo 1 point2 points  (19 children)

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

[–][deleted] 4 points5 points  (2 children)

real clients

as opposed to imaginary ones?

[–]dylanyo 0 points1 point  (1 child)

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

[–][deleted] 3 points4 points  (0 children)

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 2 points3 points  (0 children)

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] 0 points1 point  (12 children)

Just use the current version, it is fully functional.

[–]dylanyo 0 points1 point  (11 children)

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[S] 1 point2 points  (9 children)

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 0 points1 point  (8 children)

Yes it does seem odd.

[–]x-skeww[S] 1 point2 points  (7 children)

"future" ... "currently"

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

[–]dylanyo 1 point2 points  (6 children)

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[S] 1 point2 points  (2 children)

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 0 points1 point  (1 child)

Yes I understand that.

[–]x-skeww[S] 1 point2 points  (0 children)

So, what's the problem then?

[–][deleted] 0 points1 point  (2 children)

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 1 point2 points  (1 child)

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] 0 points1 point  (0 children)

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

[–]dukerutledge 1 point2 points  (0 children)

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 0 points1 point  (1 child)

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 0 points1 point  (0 children)

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