Linked by Thom Holwerda on Fri 12th Jul 2013 12:01 UTC
Windows The general gist? A minor update somewhere this year, but the real update won't come until 2014. In the meantime, we'll have to... "Resuming..." ...settle for CardDAV/CalDAV support, some additional HTML5 support, and fixes for Xbox Music metadata. We were promised regular updates and an early access program for enthusiasts - but Microsoft failed to deliver, once more. For all intents and purposes, thanks... "Resuming..." the switch to the Windows NT kernel, the Windows Phone we're using today has very little additional functionality to offer over what we were using on WP7 release day. I've been a Windows Phone user since WP7 release day, but Microsoft has lost me.
Thread beginning with comment 567071
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:

What about the fact that IE10 (fully patched) still does not work with some websites that handle Chrome and firefox and importantly IE9 perfectly well.

We have banned IE10 from all our systems.
IE9 with is frequent crashes is bad enough but IE10 fails to render a load of sites that IE9 at least handles half decently.

If this is progress according to MS then I'd hate to see what happens when they really go into decline.

Reply Parent Score: 1

Nelson Member since:

I can't begin to comment without knowing specifically why, but my guess is that those websites have faulty feature/browser detection that causes them not to work.

If you're curious, I'd try those same websites with IE11 which goes a good way towards overcoming some of the obstacles thrown their way by web developers who mistakenly think that IE can't handle certain features.

Also, there are some things that IE does better than Chrome/FF and vice versa. This is the point of competition.

I don't think its a bad thing that IE is on a yearly release schedule now and gaining more standards support (and even WebGL, surprisingly) at a faster pace.

Reply Parent Score: 2