3 ms·
Yes, it's slower and takes more RAM than JPG. I can see a delay of about a second in my browser. (Edit: I assume my browser is caching the data, but if not, som
by sp332 12y ago
Yes, it's slower and takes more RAM than JPG. I can see a delay of about a second in my browser. (Edit: I assume my browser is caching the data, but if not, some of that time could be re-downloading the data.)
- Xorlev 12y agoIf the decoder wasn't in JS, that might not be the case. It'd undoubtably be a more efficient native implementation (possibly with hardware support) were it integrated.
- deleted 12y ago[deleted]
- biot 12y ago[Edit] I had misunderstood the quoted Mozilla performance claims[0] to be related to processing speed, whereas they refer to performance being a measurement of quality. Thanks sp332 for the correction. [0] http://people.mozilla.org/~josh/lossy_compressed_image_study_july_2014/ http://people.mozilla.org/~josh/lossy_compressed_image_study...
- sp332 12y agoCompression performance does not mean speed. It just means how well it compressed the images. None of the tests on that page even mention speed.