4 ms·
Props to Microsoft for 1. Breaking compatibility with WinXP for performance gains. 2. Not supporting non-finalized web standards.
by vecter 16y ago
Props to Microsoft for
1. Breaking compatibility with WinXP for performance gains.
2. Not supporting non-finalized web standards.
- mccutchen 16y agoTrue, but lack of XP support combined with XP's 40-50% market share in early 2011 (http://en.wikipedia.org/wiki/Microsoft_Windows#Usage_share http://en.wikipedia.org/wiki/Microsoft_Windows#Usage_share) means that this great new browser might take a long time to gain traction.
- MatthewPhillips 16y agoActually I disagree with point #2 because their definition of "finalized" is stuff that other browsers have done for 2 years. Are we really going to have to wait another 2 years for cache.manifest, geolocation, web fonts, web sockets, web workers, drag and drop (and many other things that I can't think of off the top of my head)?
- kenjackson 16y agoWhy don't they just finalize these things and put MS's feet to the fire.
- ck2 16y agoBut Chrome, Firefox and now Opera are getting the same if not better performance gains without breaking XP compatibility.