Thanks for sharing Ankur.

I bumped into this article recently – https://meta.discourse.org/t/the-state-of-javascript-on-android-in-2015-is-poor/33889

It seems Android has its issues as well, which puts JavaScript in a very worrying position in mobile. You either get a low performing Android or an iOS device lacking in newer HTML5 standards.

I agree. Its also notable that Apple released CloudKit for JS in this year’s WWDC (https://developer.apple.com/videos/wwdc/2015/?id=710). I see their investment into the web platform as slow and more discriminating. They seem to pick the parts of the web they care about and help them evolve (high density images for retina screens, touch events, icon formats), and leave the “costly” features that they would rather see thrive in native out of the picture.

As a web developer and a user of Apple’s platforms, it makes me very sad. We, as developers, need to continue to push forward and let Apple and Safari know that if they don’t keep up, they will be left behind.

What is sad is that the whole smoke and mirrors about supporting web standards was a just that, a big lie. But Apple fanbois still cannot see through it, and even defend it.

Flash aside, the fact that the web is being downgraded to a second class citizen by walled gardens is something we should all be concerned about.

Thanks Sime – I stand corrected.

I find the opposite to be true. WebKit has recently improved quite a bit. They have a revamped Twitter account where they share what they’re working on. Among other things, Shadow DOM and ECMAScript 6. Just today, an Apple engineer has asked on Twitter what they should be focusing on regarding SVG.