./configure --size-limit=640x480 --enable-small --enable-small trades speed for size. It disables loopfilter optimizations and reduces memory overhead. For embedded decoding, this is often invisible to the user. Yes and no.
From the perspective of a desktop Linux user: libvpx is lean, fast, and necessary. The "bloat" is actually future-proofing . bloat libvpx
The problem isn't Google's code. The problem is that the open-source ecosystem has standardized on a as the default. We need better documentation for "embedded" or "minimal" profiles. Yes and no
./configure --disable-runtime-cpu-detect --enable-static This tells the compiler: "Don't write the dispatcher. Just write the code for the CPU I am sitting on." This can cut binary size by 30-40%. Don't need VP8? (You probably don't; you want VP9). Or vice versa? You can't fully disable one easily, but you can reduce features: The problem isn't Google's code
We aren't talking about malware. We are talking about feature creep .
From the perspective of an IoT developer with 32 MB of total flash storage: The default libvpx is a nightmare of redundant symbol tables and CPU dispatchers that will never fire on their hardware.