:) If you want to complain to Apple that they need to step up their game and actually support modern web APIs on Safari, I'm all for that, I'll be complaining right alongside you. I can even throw other APIs onto the pile, Safari is the only modern browser that doesn't support device vibration.

To be fair to the original thread, Apple has always tried to protray that it's doing something brave or prescient by dropping technologies or introducing proprietary standards, and it's pretty clear that they were not actually interested in the Open web when they dropped Flash. I do think Flash was dropped in a clumsy way, and I would try to separate Apple's clear push to try and monopolize the mobile games market and kill web games from the actual push for the Open web as an application platform.

I think Apple has made it pretty clear on iOS that they don't care about the web as an application platform.

----

> In the broader scheme of things I think the next couple of years are going to be really interesting for web games in general.

I... hope so. What bothers me about the long-term future is that I'm now seeing less investment on the web side of things on APIs that I think are going to be essential to pushing web games forward in new ways. Even simple stuff like web audio, good controller layout support (also, controller rumble support please), better timing for fixed game intervals. I think the web could easily replace Flash, but there are definitely more APIs I want in general for games.

My worry is that it takes so long for the tooling in those areas to catch up that the actual APIs start to lag behind because there's not enough pressure on browser manufacturers to care about them. We already kind of saw this with Chrome breaking audio on tons of web games because they just didn't think to test them.

Best of luck to anything you're working on, I'm rooting for you.