3 ms·

HTML isn't a layout system. And yeah, of course a grid of images is going to be fast, especially if they aren't even scaled. It's literally just a blit. What g

HTML isn't a layout system. And yeah, of course a grid of images is going to be fast, especially if they aren't even scaled. It's literally just a blit. What gets expensive is when you add bilinear filtering, alpha compositing, text, shadows with blur, path filling and/or tessellation... All of those things are things people now expect from apps, native or otherwise.

stuaxo 10y ago
Not to mention decoding the image format, if there are lots then they will be swapped and it may be quicker to just decode them again
MichaelGG 10y ago
There wasn't any fancy shadows, compositing, etc. The CPU was all spent calculating layouts and doing "stuff", before the images even rendered. My guess is some suboptimal code buried by a kilometre's worth of abstractions. It's not that FF is doing something slow (that I know of), it's the mess people have built on top of HTML/JS/CSS that ends up with non-junior developers creating monstrosities.