OT - both Safari (w/o Flash) and Google Chrome max out all CPU cores as long as this site is open. The visualisation might need an upper limit on the work it is doing per second...
It made my Firefox / Windows XP / creaky old laptop freak out, too. Might putting the interactive bit on a separate page to the article be in order, so those of us without the specs to play with the interactive bit can still readily read the article?
Comments
OT - both Safari (w/o Flash) and Google Chrome max out all CPU cores as long as this site is open. The visualisation might need an upper limit on the work it is doing per second...
I'm on chrome without flash (ubuntu) and I took a screenshot of chrome using 172% of the cpu!
Here's a copy of the post with just text and screenshots: http://www.cs.utexas.edu/~elie/noscriptnetworks.html .
I developed this on Chrome on a Mac and Chromium on Ubuntu, and it worked on both of those. Sorry it's giving you problems.
It made my Firefox / Windows XP / creaky old laptop freak out, too. Might putting the interactive bit on a separate page to the article be in order, so those of us without the specs to play with the interactive bit can still readily read the article?
Firefox 19 on Window 7, and the page sails by just fine.
I would've hazarded a guess at a Webkit bug, but OP mentioned she developed this on Chrome..
It may "sail fine" but sure left my fans howling too. I don't think this is a browser thing.
Not even a hint of stress on Firefox/OSX