Years later and that still chafes my ass.
Look, fifteen years ago, my 200MHz Pentium 1 (which was more than twice minimum spec) was running Quake 2 at fully playable speed, using purely software rendering. Not long after, I tossed in a 1998 Voodoo2 card, and had it running a full 60 frames per second at what today would be considered HD resolution. (Yea, I used to be a hardware whore, believe it or not.)
Are you shitting me?
Oh, and what exactly do you think all that computational masturbation is doing to your battery life?
So...how much exactly did you pay for that shiny new 2012-model Pentium 1 of yours? Congratulations, you got yourself shafted. You must be proud.
Ok, but wait, there's also WebGL Quake 3. Hmm, yea, running the CPU-side of a GPU-bounded program in JS really proves your quad-core isn't getting castrated into a battery-guzzling Pentium 2.
So, web 2.0 clouds-for-brains, how about writing an HD video transcoder in JS that actually compares to real software? Or hell, a JS version of any native code that actually requires a CPU from this fucking decade. Basically what we're looking for is a "JS isn't slow" demonstration that's not constructed out of strawmen. Do that, dear web crowd, and then I'll accept that you ignorant assholes aren't ruining technology.