Play PacMan at google.com Now.
google.com
google.com
Welcome to HN by the way.
EDIT: You wouldn't happen to be Rodger from the nonlogic community, would you?
How's it shakin'?
g.level == 256 && g.killScreen()http://news.ycombinator.com/item?id=1367899
Edit: actually it seems this post one is older. Hadn't seen it :(
That's what they get from not using Canvas or any other technology newer than 10 years old. The game is built of 8x8 pixel DIVs.
This has the same side effect for Google regarding ads as does the button. Although if a user wants to be taken directly to website ABC they prob aren't a good audience for ads.
For example, in Chrome, add this as one of the Search Engines in the options dialog: http://www.google.com/search?q=%s&btnI=Im+Feeling+Lucky
I've associated that with the keyword "gg"
Now, when I go to the address bar and type a query whose first Google result I am confident will be the destination I want, I've got a great way to get there.
Example:
"gg imdb Forest Gump"
Will get me to IMDB's Forest Gump page. So you can pretty much imagine the power here, especially for reference sites. Type the site name and the query, and you'll end up where you want to be.
Most of those sites has an opensearch provider.
http://mrgan.tumblr.com/post/257187093/pie-guy
http://mrgan.com/pieguy/ <-- go here on your iphone
EDIT: I didn't see that you had to click "Insert Coin" to start.
I experimented with <audio> tag in HTML5 game few days ago: it's fine for media player type applications (where you play longer sounds with looser coupling to user actions), but it's not there yet for games (implementation-wise, API is ok).
If you need to play a lot of tiny sounds in rapid response to player actions, you are going to get random weird behaviors and cross-browser inconsistencies: noticeable lags, cracking noises, cuts and repetitions.
Ogg Vorbis and (of course WAV) works quite nice, MP3 doesn't. For Safari, maybe AAC would be the right choice. Still, as you said, the <audio> implementation is quite buggy at times. But I have no doubt it will get better!
And it's not just encoding, it seems to be dependent also on what's inside the sound file like a particular waveform or length.
For me the worst were a sequences of very short sounds (fractions of second) played in a direct response to rapid successive keypresses (keydown-keydown-keydown should make pew-pew-pew). No matter what I did, there was always at least one browser with some showstopping bug.
javascript:(function(){var rancidbacon={};try{rancidbacon.com=document.getElementsByName("pm-sound")[0];rancidbacon.com.parentElement.removeChild(rancidbacon.com);}catch(_){}})()
More details here: http://stuff.rancidbacon.com/google-pacman/
how senior did the approval have to be to get this allowed, do you think?
http://operandx.com/GooglePacman/Play.html
Enjoy!
(no, not really)
Awesome :)
I liked the plain old google page .. simple
My score.