4 ms·
> The WASM is only 311kb That's gargantuan.
by Jyaif 4y ago
> The WASM is only 311kb
That's gargantuan.
- samwillis 4y agoNot if you have 10mb of images on the page... at that point it makes a significant saving.
- yakubin 4y agoWhich is 1-2 full-sized photos from a 30Mpx camera. More if it’s just thumbnails.
- Jyaif 4y agoYes it will save bandwidth in many cases, it doesn't change the fact that for an image decoder 300KB is huge.
- lifthrasiir 4y agoIf you are going to leverage vectorization for performance (and WebAssembly does support 128-bit vector instructions), it's very much inevitable for binary size to increase.
- pizza 4y agoI'd agree with that if it were about a JPEG decoder - JPEG is a simple algorithm. But JPEG XL is really quite complex. Like kinda really complex. It is better described as a mixing pot for lots of different, individually-impressive contributions to image compression accumulated over years of open source iteration, rather than a succinctly describable algorithm. like it would be better to call it a hybrid of the existing flif/fuif/lode png/pik/brunsli/guetzli/gritibanzli/butteraugli/gralic projects, and it's also using libhwy for cross-platform simd. 311 kb, to run that via js, is amazing, imo.