Well let's see, there's probably something in the drawing co-

Four full-sized canvases laid atop each other?

(And I guess peeking at the code, they may be able to get rid of one of those Math.sqrts by using the distance-squared everywhere you need it instead of the distance. As a first pass there's probably other sqrts or trig that could be removed, but its hard to eyeball minified code)

I thought it was a very pretty sight, but it probably could be made a lot less harsh.

Hey hey. Sorry about that. This is Ashley from Parse and we're working on it. If you notice any more issues or anything shoot me an email at ams at fb.com.

Oh I thought you were trying to show that HTML is a graveyard and native is the way forward.

While I fully agree with the senselessness of this overlapping-parallaxing-animating background drivel I did notice it seemed to work rather well here, using about 52% CPU on an Athlon II P360-powered machine (not the fastest around) running Firefox 30 on Linux. This is still 50% more than I'd like to see once the page has rendered, but for that purpose I have noscript and friends - I actually had to allow scripting on that page to see the animations in the first place...

I think there's some cross-browser optimizations to be done here, because it completely destroyed Safari for me, and that's on a pretty serious machine (2.7 i7, 16GB RAM).

It actually causes latest Chrome on my 2011 Macbook Air to go slow enough that I can't scroll down the page. I guess if I open up Developer Mode and extract the text, I could find out what's going on.

It looks pretty cool though.

it looks beautiful but just having the page open on my 2011 Macbook Air results in about 50% constant cpu usage, fans spinnig up etc without me doing anything. Thats a bit much.

The mobile view doesn't have the CPU crazy rendering, just an unreadably long page with a hard to read bizarrely kerned navigation menu hiding behind the hamburger icon.