>
Sadly, looking at that table, it's clear that Safari is the one dragging their feet. Full support for ES6 in the latest Chrome, FF, and Edge, but very poor support in the latest Safari.Actually Safari (well, Webkit), in beta, is the closest to full ES6 support of all current browsers -- down to 98% or so.
It's just that Safari has a release only once or twice a year. But when it has, suddenly everybody on OS X/iOS using Safari would get all that stuff at once.
(And recently they started a public beta builds program that might see them releasing new versions much sooner).
>Apple recognizes that the Web poses a threat to their business model
And with that information above, can we put this age old conspiracy theory to rest?
Apple had long had the best mobile browser when Android still had the horrible "Android Browser". They regularly added all kinds of features that benefit apps (e.g. the canvas, css animations, several API to access native mobile features, etc.), and they continuously improve it (see this 98% ES6 support).
For a company that "fears web apps" Apple not only promoted them to developers (before and after they created their native app frameworks and app store), not only has extensive documentation and how to's for best mobile experiences on their dev pages, but also has seen that Safari webkit based apps have traditionally been a better experience than Chrome based web apps on Android.
Even today, it's faster, and more memory/cpu/battery efficient on mobile than Chrome is on Android.
https://blog.runspired.com/2016/03/25/the-chrome-distortion-...
Safari was only held back because it's not a huge priority for Apple -- not because of some fear that web apps will eat their app store lunch.
After all, web apps are difficult to monetize (no credit cards at hand), people expect most of them to be free, have a subpar experience for anything more demanding compared to bare metal languages, and don't integrate that well with native APIs anywhere (iOS, Android, Desktop, etc), as they have to run in a more restricted sandbox than native apps do (and of course somebody has to continuously porting all the native APIs, and at a great common denominator at that, since they also need to be portable).