2 ms·
It is a good idea. When WebAssembly becomes more widespread, it is likely we can drop fixed encoders altogether. Though at this stage the performance impact mig
by miohtama 3y ago
It is a good idea. When WebAssembly becomes more widespread, it is likely we can drop fixed encoders altogether. Though at this stage the performance impact might be still too much to warrant anything like this.
- toastal 3y agoSo every website would ship with its own codecs? There aren’t shared caches across domains. Why would anyone choose that much latency+badwidth+compute (which new require JS enabled) to use a new codec over the native ones? Certainly not the small–medium sites.
- miohtama 3y agoBecause of the total saved bandwidth. Codec binaries are few hundred kb at most, while high quality images are dozens of megabytes.