News for hackers. Stuff that matters.
Re:Introducing Paper by acdha on Thursday January 30, 2014 @10:24AM (#7151091)
This is why WebM failed: on my (old) 2010 MacBook Air Firefox uses 100% CPU on two cores and it's still barely hitting 1fps with stuttering audio. Safari uses the native hardware-accelerated H.264 so it plays back perfectly at 15% of one core. Chrome's sandbox implementation appears to be less efficient so it's 80% but again, still perfect.

The vp8 developers clearly made some attempts at optimization – profilers show a lot of time being spent in an SSE3-optimized decode path – but that's a long, slow game trying to catch up with years of significant software and, later, hardware optimization.

There are no comments on this comment yet.