Nim can execute code at compile time and store them in constants. http://nim-lang.org/manual.html#const-section example: http://hookrace.net/blog/what-is-special-about-nim/

http://ruletheweb.co.uk/matrix.html 1024 Bytes, off by 10x

Although interestingly this version is not as pretty and much slower.

I'm sure is just a matter of tweaking it...

Awesome but your vanilla JS version uses more CPU than GopherJS (at least in my laptop), any idea why?

sorry, not mine, found on SO http://codegolf.stackexchange.com/questions/17285/make-the-m...

If I fill out the phone number all the way, then go back with the arrow keys and try to delete/change numbers, I get weird behavior

thanks for the feedback, I see the error as well. I created an issue and will take a closer a look.

From what I can tell it looks like it's using the Chromium Embedded Framework

http://code.google.com/p/chromiumembedded/wiki/GeneralUsage

The only thing I found that was similar was holding down shift and drag selecting with the right mouse button.

I had the same problem too and solved it by writing build rules for WAF(http://www.l-vu.com/2012/03/21/Using_waf_to_build_web_assets...)

Sorry, about that. I initially hide everything, and use ajax/browserid to authenticate/show things depending on the status. Just altered it now to show the initial page at least, if you have js disabled.

Works now :)

I'm making something like that at http://wr173.com/

It's already on the author's github. https://github.com/yyx990803/HTML5-Clear

Maybe you can try to library for sound. SoundManager 2 does html5 sound and falls back to flash. http://www.schillmania.com/projects/soundmanager2/

Apparantly there are issues with looping (http://www.schillmania.com/projects/soundmanager2/demo/api/) but it points to (http://www.flickr.com/photos/schill/4499319436/) as a way to fix sound loops.

Regarding other technical problems: I've had that issue too with Chrome beta, using csstransforms caused my textboxes to be unclickable(but still tab-able). My solution was to downgrade to the normal Chrome version and hoped it'll be fixed by the time it hit stable.