iOS only? Meh. It really is true: iOS is the new MSIE.
Somewhere down the road iOS-only code will not be accepted, and then we have tons of code already deployed which will never work on anything else, unless Apple's non-standard JS and webkit extensions are accounted for in other browsers.
This is hopeless and pathetic. And HN will love it.
I don't understand why fun projects can't just be fun projects...why does everything have to be interpreted as some sort of statement concerning the state of the web?
Also no websocket support in Android browser yet (http://caniuse.com/#feat=websockets). This makes things a little less ideal for realtime gameplay (even with the fallback options provided by socket.io).
Should also note that DeviceOrientation (aka "accelerometer in the browser") is in Android 3.0+ (although that doesn't do much for most of the devices out there).
There are some very good reasons that, despite IE6's popularity and extreme market share--both larger than iOS, I believe--everybody else did not adopt IE6-only "features" like ActiveX as standards.
Comments
iOS only? Meh. It really is true: iOS is the new MSIE.
Somewhere down the road iOS-only code will not be accepted, and then we have tons of code already deployed which will never work on anything else, unless Apple's non-standard JS and webkit extensions are accounted for in other browsers.
This is hopeless and pathetic. And HN will love it.
I don't understand why fun projects can't just be fun projects...why does everything have to be interpreted as some sort of statement concerning the state of the web?
It's iOS only because Android does NOT support accelerometer within the browser.
Also no websocket support in Android browser yet (http://caniuse.com/#feat=websockets). This makes things a little less ideal for realtime gameplay (even with the fallback options provided by socket.io).
That's pretty sucky. Does anyone know if chrome for Android support it? I was hoping for WebGL and Websockets in 4.0 but I guess neither is around :(
This bug claims that it does: http://code.google.com/p/android/issues/detail?id=25221
The current direction does seem to be towards end-of-lifing the Android browser (and ChromeOS) and moving Chrome in as the default.
Should also note that DeviceOrientation (aka "accelerometer in the browser") is in Android 3.0+ (although that doesn't do much for most of the devices out there).
http://caniuse.com/#feat=deviceorientation
It's working with ICS, in the default browser.
It's Android's fault for not supporting the accelerometer in its browser.
Hopeless and pathetic? They make good products. Get over it and make something yourself.
If it is the only accepted code, then it is by definition stand. It is just up to the others to implement these things.
There are some very good reasons that, despite IE6's popularity and extreme market share--both larger than iOS, I believe--everybody else did not adopt IE6-only "features" like ActiveX as standards.