Just posted a summary of our thoughts on where Angular 2.0 is headed. Please let us know your thoughts.
95 plus ones
Shared publicly•View activity
View 5 previous comments
- IE10 may be on the list. We'll see how development goes.Mar 19, 2014
- Read the post, my friend, read the post.Mar 19, 2014
- : Angular used to be all about pushing the boundaries and showing us all how awesome front-end development can be. Imagine how awesome future browsers are going to be, and see how many of those future features we can simulate.
Those future browsers are here now. ES5 is everywhere, and parts of ES6 are already in stable Firefox and Chrome. I'm excited to see where Angular 2.0 takes us, and what front-end development might look like in the next couple of years.Mar 19, 2014
- ES6 & other improvements sounds great!
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.
https://developer.apple.com/support/appstore/Mar 19, 2014
- 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.:)Mar 19, 2014
- Thanks for the reply. For the polymer question, I wasn't necessarily asking for IE10 support, just whether Angular's browser compatibility list will be in sync with the Polymer compatibility list, considering that the two teams are coordinating on the Web Components pollyfill (platform.js). Currently the Polymer page lists IE10 support - will that change to IE11 now that Angular is targeting only IE11+?Mar 19, 2014