Hacker News Reader

Apple have always run on their own schedule. They just generally don't do coordination. I wouldn't take it to indicate lack of support.

View on HN

"Apple is always behind" would be a more apt way to describe their dealings with Safari.

Except WebKit and Safari are the first browser (engines) to be 100% ES6 compatible:

http://kangax.github.io/compat-table/es6/

And yet it's still not 100% ES5 Compatible, like FireFox and Edge, and still behind Chrome (98% to 99%).

http://kangax.github.io/compat-table/es5/

Getting to 100% on ES6 was pleasant, but still a surprise given their track record not just with JS support but with some CSS features too. They're often stragglers, even more so now that Microsoft's browser is getting better.

Maybe in the past couple of years, but there's a big reason why a lot of mobile browsers were based on WebKit a few years ago.

If you want to build a mobile browser that works on both iOS and Android, WebKit is the only game in town. That's because Apple doesn't allow other web browser engines to be used. If Gecko and Blink (and the upcoming Servo) were given a fairer playing field, perhaps the mobile browser market would be less tied into WebKit.

'big reason' being apple made them?

Reply on news.ycombinator.com