News for hackers. Stuff that matters.
Re:HTML 5 Asteroids by renewableGuy on Thursday May 13, 2010 @06:46AM (#1343825)
Cool. But the game is very sluggish and almost non playable on iPad. I wish these html5 games were built with some consideration for iPad.

Anyway, i really appreciate the effort. One step closer to a flash-less web.

Re:HTML 5 Asteroids by andrew1 on Thursday May 13, 2010 @07:38AM (#1343891)
> I wish these html5 games were built some consideration for iPad.

If the author doesn't have an iPad then it's going to be a bit difficult for him to know how this will perform. Possibly he's just made sure it works OK for the 99.99% of people not using iPads.

Re:HTML 5 Asteroids by Steltek on Thursday May 13, 2010 @11:29AM (#1344527)
I recall one of Jobs' major points against Flash was not providing support for touch-based interfaces. Here we have a clearcut example that the tool you use (HTML5) does guarantee you anything in the final product.

On a contrarian note, a cross-platform game framework here could perhaps provide for remappable controls and performance tuning. This same cross-platform framework is labeled by Jobs as a threat to Apple's marketshare.

Perhaps Apple should not be so quick to bludgeon developers with claims of The One Best Way to the exclusion of all others.

Re:HTML 5 Asteroids by jasonlotito on Thursday May 13, 2010 @08:32AM (#1344001)
Maybe the iPad should be built with some consideration for the web? The web shouldn't be built with consideration for a single device. The game is HTML5. Fine. The iPad obviously has performance issues with that. That's the iPad's problem. Apple didn't want Flash, they wanted HTML5 and standards. Now they have to pony up.

But no, the iPad should conform to standards, and support those standards. If the iPad is not capable of supporting those standards in a usable manner, it's the iPads problem.

Re:HTML 5 Asteroids by joubert on Thursday May 13, 2010 @11:18AM (#1344480)
I agree with both you and the parent. One of the problems with many sites is the expectation that there is a (dedicated) keyboard on the device that is browsing.

I think when one designs something like this, take cognizance that more and more devices have virtual keyboards.