61–70 of 129 posts
IBM thinkpad T61, 2GB ram, running firefox 3.6.8 for Ubuntu 9.10 (yeah yeah, I know), and Flash 10,1,82,76 . Ball is nice and smooth on HTML5 side, and kind of jerky on flash side. That could just be Linux+flash issues, but the animation for HTML5 is super-smooth, so I'm guessing it's just bad flash plugin.
On my Motorola Droid running Froyo, the flash side is much smoother. On the JS side I couldnt really control it because the browser was also intercepting every keystroke and trying to put them in the url/search bar.
MacOSX on a 2.16GHz Dual2Core Macbook with Chrome: HTML5 is really fluent here while Flash seems somehow laggy (I would guess 20 FPS or less). I think I also found a bug in the Flash version. The ball got stuck somehow at the top bar.
Make sure you've excluded the URL from Vimium/Vimperator before playing!
The Flash side was unexpectedly slow, and comments on this same article on Reddit indicate that it is because they are doing a lot of JavaScript-to-Flash communication, which is unusual for a game, as well as enabling "wmode=transparent", which allows DOM elements to be positioned on top of Flash content, slows down Flash content, and is apparently unnecessary for this page.
HTML5 does all of that out of the box without any flags, so it's a fair comparison.
This is depressing. It's 2010, and our computers have issues rendering Pong .
The only complaint I had was that there was some sort of hit detection problem on the HTML5 side (the ball got caught inside the paddle, and the rally count shot up by about 30 in about a second). I can't hold it against the HTML5 code though, since the flash side did it to me too about 10 seconds later.