Trying to compile code to JavaScript results usually in sub-optimal performance. You have to manually do it to tweak the best performance out of the language. It's kinda retarded, but it's analogous to writing assembly code for performance critical apps. Also, I did it for the lulz.
Chrome runs the JavaScript execution the best, while sucky at graphics (Scaling via CSS is sluggish in chrome).
Firefox 4+ runs it overall well (Slight GC hiccups in Firefox 9 though).
IE9 runs it like crap (JavaScript execution is like firefox 3.6, slow as hell).
Opera 11.6 can't run it, because it doesn't follow the typed array spec, causing the emulated cpu to crash. Works in older opera versions though, but just a little faster than IE9.
Safari 5.1.X reloads the page when ever a game starts, because of a js engine regression that happened in safari 5.1.1. Works in webkit nightlies though, and Safari 5.0.X
Because I added a different version of Tetris than the one most people know. I should probably switch the one there with the later version that changed out its music.
Encryption is inadequate because others can still find out what your password was (Insert disgruntled employee or hacker that gets the master decyption key).
A website employee should only be able to reset the password at most if the passwords is properly SALTed or hashed. Storing passwords in plaintext or not hashing them had to be done. It's insecure to just encrypt the password and rather not hash it.