You can also get really small file sizes by ignoring frameworks and porting unsupported codecs to wasm.

I ported jbig2 (17kb uncompressed) and codec2 (60kb uncompressed) to wasm which enables me to use really small image and audio files in my web app. I also made a custom read only database and search engine with built-in zstd decompressor (39kb uncompressed). It probably wouldn't run on a psp though.

I like optimizing and making things small. I want to use neural audio codecs for even better compression but the model sizes and compute complexity are major hurdles and muddy the vision.

▲

mrpf1ster a day ago | parent [-]

I hope the image and audio bandwidth savings are more than the cost of having to send down the codec JS payload - might be worth it for a web app with a lot of image/audio loading

	▲	tnelsond4 a day ago \| parent [-]
		With a 17kb jbig2 decoder all you need is a few one-bit images (a page of a book scan) for it to save bandwidth. With a 60kb codec2 decoder you need about 2 minutes of audio to start saving. But the target is dictionary apps with thousands of seconds of audio and thousands of images.