Hacker News new | past | comments | ask | show | jobs | submit login

Why Safari is the new IE:

- No WebRTC (http://iswebrtcreadyyet.com)

- No Service Worker (https://jakearchibald.github.io/isserviceworkerready)

- No WebM/VP8 support

- No ASM.js

- No MediaRecorder

Combined with the following policy decisions from Apple:

- Almost complete lack of engagement with the community

- Default browser on iOS

- No alternative rendering engines supported on iOS. (This is even worse than IE, as users could always install third-party browsers on Windows)

- Safari updates tied to OS updates, which mean users of old iPhones are stuck on old Safari versions because they don't get OS updates anymore

Oh please. As many of the commenters have said, if you think Safari is the new IE then you weren't around when IE was the dominant browser.

Both WebRTC (https://webkit.org/status/#specification-webrtc) and ASM.js (https://webkit.org/status/#feature-asm.js) are under development.

Service Workers are under consideration: https://webkit.org/status/#specification-service-workers

Regarding community involvement, the WebKit team seems more responsive and accessible than in the past. When one of the developers said he was available to fix CSS bugs (https://twitter.com/grorgwork/status/738486146313773057), I tweeted at him a bug that had been annoying me.

A few days later, it was fixed: https://twitter.com/grorgwork/status/740356645981585408

Things are different now and going in the right direction.

> A few days later, it was fixed: https://twitter.com/grorgwork/status/740356645981585408

However, no iOS users will see this change until iOS 10 is released. (Hopefully this makes it into 10, instead of waiting for iOS 11).

I can confirm--because I'm running the public beta of iOS 10--that the fix (and many others) are in Safari 10, a core component of iOS 10.

And just like we see every year, the latest release of iOS will be released in September, so it's just a couple of months away.

All of those APIs are the gravy on top of cherries. Most websites don't even use them. IE9 and older blatantly ignored and/or reimplemented key browser functionality such as rendering and DOM querying APIs. It was a mess. Whatever Safari is or isn't doing doesn't even compare.

Forgot to add a few more WebKit features:

- Slot-Based Shadow DOM API (https://webkit.org/blog/4096/introducing-shadow-dom-api/)

- Wide-gamut color support (https://webkit.org/blog/6682/improving-color-on-the-web/)

- 100% ES6 support (https://twitter.com/webkit/status/728643624464883712)

- new JIT compiler (https://webkit.org/blog/5852/introducing-the-b3-jit-compiler...)

- 88% CSS support (CSS1 through CSS4, via http://css4-selectors.com/browser-selector-test/)

It appears that Safari supposedly being the new IE has been greatly exaggerated.

Let's not forget that both iOS and Android cripple HTML5 apps so as to favor native app development. I'm not a JS/HTML/CSS fanboy, but it's still a move to increase lock-in.

Any evidence to support this?

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact