3 ms·
The codecs in WebCodecs also requires bandwidth to download. So they could do this by moving codec support out of the existing APIs, with an auto-fallback to a
by mike_hearn 4y ago
The codecs in WebCodecs also requires bandwidth to download. So they could do this by moving codec support out of the existing APIs, with an auto-fallback to a default WebAssembly module if you don't specify one when instantiating the API, thus de-privileging the renderer code and keeping things size equal whilst still allowing lower level API access.
That's kind of my point: they don't seem to act in a way that suggests WebAssembly is a way to implement features with competitive performance and overhead.