Updated subject to be more explicit. On Tuesday, July 21, 2015 at 6:59:31 PM UTC-7, John Livingston wrote: > > *Intro* > > This may be a bit premature since *Angular 2.0* is still in alpha and we > likely won’t have any news about release dates or betas until the October > conference. However, given the rapid change in the industry and the > proliferation and advances of competing frameworks like Ember, React, > Meteor, and even Aurelia, I feel compelled to think about what I should be > recommending to my customers and where I should be investing my dwindling > time. > > > *Legacy Browsers* > > > - Microsoft is dropping support for IE9 in January and that Windows 10 > will likely have an impact on legacy IE market penetration. > https://support.microsoft.com/en-us/gp/microsoft-internet-explorer > - It is no secret that huge number of IE8 and IE9 stats are based on > pirated versions in China and Southeast Asia. ( > http://www.upsdell.com/BrowserNews/stat_trends.htm) > - I have worked for and with large enterprises and know that many IT > departments will be reluctant and very slow to adopt new OSs and new > browsers. (A bit anecdotal, but we all know it is true. :) ) > - I work on several projects with large older populations that are > notorious about not updating their machines. (Very anecdotal. :) ) > > *Statistics* > > The latest statistics show that a whopping 26% are still using legacy > (pre IE11) IE browsers. (See below) While I can still continue to use 1.x > and write code that is more 2.0 friendly, I frankly don’t have much faith > that simply coding in TypeScript and using John Papa’s excellent style > guide <https://github.com/johnpapa/angular-styleguide> (sorry Todd) will > magically make it easy for me to upgrade when the time comes. Obviously I > can mix and match things like React with Angular 1.x to get better > performance, but honestly who really wants to do that? Furthermore, can we > really predict when evergreen browsers become a reality? Google resident > and technorati bad @$$ Paul Irish was Google +ing about this (among other > things) years ago . ;) > https://plus.google.com/+PaulIrish/posts/eqmZ1dkScjY > > > My apologies for the longwinded introduction, but I hope you can see where > I am coming from... > > > *The Question* > > *Are there any plans to provide a combinations of shims and/or polyfills, > and/or transpiling to ES5, or perhaps an AMD solution to provide better > support for legacy IE versions? * > > Have you hired any actuaries to do statistical analysis on legacy browser > marketshare degradation? Okay, maybe that was a tad snarky. ;) > > > *Browser Market Share* (Don’t trust the W3 school stats as they are only > relevant to the site. I'm sure Google has much better statics internally.) > > > https://www.netmarketshare.com/browser-market-share.aspx?qprid=2&qpcustomd=0 > > > *BTW*: I have been a long time advocate of Angular and have used it and > introduced it on numerous projects. Though I was a bit thrown off by all > the big changes in 2.0, after watching most of the ng-conf and ng-vegas > videos and reading numerous blog posts, I have definitely warmed up to it > and was even toying with using 2.0 on a future project. I was really > looking forward to the refactorability of TypeScript, performance > increases, and the organization and conciseness of the new framework. > > > *Disclaimer*: My first job in software was 15 years ago as a contractor > at Microsoft, working on the localization of IE 5.5 of all things (I speak > Japanese.). That said, I’ve been a loyal Chrome user since it came out in > 2008 when it was still beta. Might have to check out Spartan though. Maybe > it will use V8, webkit, and support OSX. ;) >
-- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
