[throwaway2016a]

My expectations were pretty low. I was expecting it to be doing something with the user's consent or using some sort of UX anti-pattern to trick the user into doing it. I was pleasantly surprised.

As far as performance. It didn't do enough to spin up my fan. My CPU only went to 30% (inclusive of all the other apps I have running (using Chrome on OS X).

I was under the impression most browser limit how much CPU the Javascript thread can use because of the good old days when writing a tight infinitely loop in Javascript could freeze someone's computer.

[Zetaphor]

That's not entirely the case. Just this weekend I managed to crash my browser multiple times after forgetting to clamp a loop that ran multiple canvas operations. CPU shot steady to 100% and my entire system locked up for a bit.