Comment

Comment by keenankaufman

Glad to see this working completely client-side. I've been packing my own versions of libheif and libjxl using Wasm in a web application, and what got me was memory consumption on mobile Safari. Decoding a 48-megapixel picture to RGBA is ~190MB of memory usage prior to doing anything with it, and the page is killed by iOS far before you even approach the limits of wasm32. Do you pre-scale inputs if they're larger than a certain size when tracing?

No comments yet

Be the first to share your thoughts.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton