Linked by Thom Holwerda on Fri 1st Aug 2014 18:06 UTC
Internet Explorer

Based on your feedback, we pursued a web experience for IE users consistent with what is available on iOS and Android devices - even where this meant we would be adding non-standard web platform features. We believe that this is a more pragmatic approach to running today's less-standardised mobile web.

Thank you, web developers, for turning mobile Safari into the new Internet Explorer. Have you people learned nothing?

Permalink for comment 593606
To read all comments associated with this story, please click here.
Comment by thegman
by thegman on Sat 2nd Aug 2014 03:44 UTC
thegman
Member since:
2007-01-30

I'm not a web developer, but the 'have you people learned nothing' comment shows the lack of understanding that people have about the web. It's a lovely idea to think that all web developers should write to open standards and it wouldn't matter what web browser you used.

The reality is that the web is a platform, and a hugely complicated one. To make matters worse, it's not no real compile time or runtime integrity, i.e. you don't really know if something will fail until it fails. Then of course you've got lots of users using non-cutting edge browsers, a year or two old or older even.

That basically means that web sites can, and do fail *a lot*. Whether you write to open standards or not, your site is going to fail. So you can decide to hammer out the issues on all browsers, or just pick one.

Most people writing web sites aren't doing it for the glory of HTML5 and CSS, they're doing it because it's their job, or otherwise to achieve a goal. That means working in the circumstances in which they're in.

I'm not a web developer, but I've made websites in the past. In those days you wrote for IE compatibility, and while I rolled my eyes at that, I also was pleased that I only had to test on IE, not everything else.

The web is an incredibly complicated and fault-prone system, writing to one engine, WebKit is not good for the Internet, but it's good for those making websites. By working to ensure full operation on all browsers, you're making work for yourself and all you'll be left with is a broken site on all browsers, rather than a chance at functionality on one of them.

It's not about 'learning nothing', it's about accepting the reality that the web is a total nightmare to work with, and this minimizes the nightmare.

Reply Score: 1