Clearly the author doesn't fully grasp the complete and utter hell IE provided designers dating back to the late 90s. IE simply broke everything. Safari doesn't do this in the slightest.
The title is certainly hyperbolic, and the real pain with IE for me was that the basics were so fundamentally broken. Most of the features referenced in the post are relatively new and not core components.
With that said, it is a well written post and he does make some good points. The fear for me is Safari stagnates. IE6 was a solid browser, at first. But Microsoft largely abandoned it, and it gradually became the browser everyone loved to hate.
Furthermore, the author does not claim Safari is the new IE6. He is simply demonstrating how safari is browser falling behind web standards, as IE used to.
It's such a shame you can't set a different default browsers on iOS.
While it's not as bad as IE was, I've come across enough bugs in iOS Safari that I have to agree with the author that Apple is purposefully dragging its feet.
Here are a few that I have personally run into:
As of Safari Mobile for iOS 7.1.2, tapping a clickable element causes the element to enter the:hover state, and the element will remain in the :hover state until a different element has entered the :hover state.
All of these bugs combine to make it very, very difficult to create a native feeling web-app on iOS.
I thought we were talking about Safari, not Safari Mobile. They share the name but are quite different beasts.
My main problem with using anything other than Safari when designing/coding on my MBPr is that once I start doing anything intensive like watching videos (tutorials, etc.) on Chrome, my computer sounds like it's about to take off. I've also noticed that my computer runs about 20-25 degrees hotter when using Chrome over Safari, not to mention it devours my battery.
I know this doesn't change the fact that Safari is lagging from a dev standpoint but I thought it was worth pointing out.
My MBPr is last year's model with 16GB of RAM, FWIW.
showing a brazenness even beyond that of 90’s-era Microsoft
Someone managed to either repress IE5.5 and IE6 out of the sheer horror or has conveniently forgotten how bad it used to be.
If anything Firefox is the new IE seen as it dragged it's feet for YEARS on web video, forcing everyone to deliver encodes in the crummy ogm format.
But yeah I'm sure 4 edge technologies not being included yet is way worse for web devs than YEARS of not supporting the most popular hardware accelerated video coded ever.
This is true in terms of release schedule.
However, I otherwise disagree with this - Chrome is more like IE in that it introduces bleeding-edge, Blink-specific features that other browsers have to rush to implement. -webkit prefixes are flooding the web.
Sites that say browsers like Firefox aren't supported should not exist. It's not hard to build a site that's supported by all major browsers. Unless it's some weird experiment, it just shouldn't exist.