10 ms·
I like the end result, but i'm not sure why they decided to use 14 canvas tags when 1 would have worked just as well. It seems wasteful, canvas was designed sp
by beeglebug 13y ago
I like the end result, but i'm not sure why they decided to use 14 canvas tags when 1 would have worked just as well.
It seems wasteful, canvas was designed specifically to allow drawing and manipulating multiple images on a single surface, these guys are using canvas as if it were a div with a background image.
- robin_reala 13y ago…which makes me wonder if CSS animation on stacked divs would be more efficient too?
- martin-adams 13y ago...or an animated GIF
- PavlovsCat 13y agoIf you layer several animations with varying and carefully selected run times over each other, the result never exactly repeats itself. Good luck recreating that with one GIF animation :D
- tvararu 13y agoAn animated GIF would weigh a lot more.
- kilian 13y agoMaybe they found it performed better, like Adrian Holovaty found for soundslide: http://www.holovaty.com/writing/in-defense-of-canvas/ http://www.holovaty.com/writing/in-defense-of-canvas/ (see "stacking canvases")
- robin_reala 13y agoStacking canvases makes sense when you have ones that either only need to be built on startup or change infrequently. If everything in your animation is moving (like this one) then there’s no performance benefit.
- ricardobeat 13y agoAre you sure about that? Would be interesting to see a performance comparison.