3 ms·
Disappointing, perhaps, but somehow it still manages to be better than Opera and Safari (Windows Safari, at least) for HTML5 games based on my testing [1]. Goin
by kevingadd 14y ago
Disappointing, perhaps, but somehow it still manages to be better than Opera and Safari (Windows Safari, at least) for HTML5 games based on my testing [1]. Going from last place to third place in such a short time period is an achievement in my book, even if I'd still never use IE as my primary browser.
Admittedly IE10 is still missing some features I would mark as important for game development, but when I contacted some IE devs over at Microsoft (just send an email!) they got back to me with simple workarounds that made it possible to get my games running with a few lines of additional code. (Not IE-specific code either, just clever feature-detection fallback for any browser.)
Here's how I suggest looking at it instead: Holy shit, the browser that comes stock on Windows 8 can actually run a large majority of HTML5 games and applications! You don't have to nag people to install Chrome or Firefox just to use your app! Sure, you want them to upgrade anyway - and they probably will - but that's something!
Now if IE11 comes out and doesn't advance the state of things here I'll certainly be disappointed, but at present I'd say I'm actually quite pleased: in the jump from 9 to 10 MS has brought IE forward enough that you can run HTML5 games in it without having to write a ton of browser-specific hacks or feature implementations.
WebGL support would be nice, but you still can't rely on WebGL in HTML5 games anyway since it doesn't work on a large percentage of desktop machines and is basically unusable on mobile. I think this is another area where the pressure should be on MS to get a rock solid implementation of WebGL into IE11, not to complain about IE10 not having an API that is arguably still not ready for prime time (Though increasingly close).
Complaints about not having the Web Audio API are similarly missing the point since you can't use it anyway unless you're writing a Chrome Experiment - your real complaints should be reserved for the fact that IE still has an undocumented limit on the number of live <audio> instances you can put in a single page, or for IE's latency when playing new sound effects.
Finally, allow me to repeat others' comments that it's incredibly stupid to benchmark a canvas-based game against a webgl one and present the numbers side-by-side with a straight face. Canvas performance is miserable in every single browser and IE has nothing to do with this. IE actually has one of the better Canvas implementations out there. The fault lies with Canvas being a poorly-specified, poorly implemented API, not with IE.
[1] I regularly test all my HTML5 game ports across the major browsers and regularly hit crash bugs in Safari and Opera. Also, Windows Safari still can't play back audio which is... inexplicably stupid.
- davedx 14y agoIs Windows Safari still actually developed at all?
- TazeTSchnitzel 14y agoNope, it was silently killed.
- gmac 14y agoHmm, seems pretty irresponsible of Apple to do that, given that it's thus going to go unpatched and its users will become progressively more vulnerable, no?
- TazeTSchnitzel 14y agoApple doesn't really seem to care much about responsibility or security.
- kevingadd 14y agoThis is good to know. I had assumed up until this point that it was merely behind the curve (I've been using WebKit nightlies since they're labelled as Safari...)
- masklinn 14y agoSeems as dead as Snow Leopard's: latest version is 5.1.7 (webkit 534.57.2); current version is 6.0.2 (webkit 536.26). For comparison, Chrome 12 used webkit 534.30, Chrome 20 used webkit 536.10, Chrome 23 uses 537.10.
- TazeTSchnitzel 14y ago>somehow it still manages to be better than Opera and Safari (Windows Safari, at least) for HTML5 games based on my testing Same here. I still note that IE9 and IE10 run some things a lot smoother than Chrome.
- AshleysBrain 14y ago