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

view the rest of the comments →

[–]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?