3 ms·
The only reason to extend the standard if you can't implement required functionality with acceptable performance within this standard. That is the weak point fo
by vbezhenar 7y ago
The only reason to extend the standard if you can't implement required functionality with acceptable performance within this standard. That is the weak point for web platform: JavaScript is too slow and does not have access to drivers, you can't implement GPU-accelerated H.264 video codec within browser, so you have to implement it with C++ in browser. That means that proposed standard should be Turing-complete, provide C++ level of performance and native access to required hardware, while keeping browser-level safety and isolation. That is hard thing, but I believe, it could be solved using modern virtualization techniques with some advancements from OS and hardware to better virtualize GPU, USB, etc.
- qwerty456127 7y agoI could never understand why does a browser even have to know what codec is used in a video (let alone implement it) when there are ffmpeg, DirectShow and whatever the Apple alternative is. Same thing with picture formats: if I were developing a browser I would just support them all via ImageMagick or something like that.
- vbezhenar 7y agoAFAIK until recently there was no support for H.264 in DirectShow. So your browser would not be very useful. Also you wouldn't be able to control video from JavaScript (get current time, get current loaded amount, play, pause, stop, etc).
- qwerty456127 7y agoThen just stick to ffmpeg, libav, gstreamer or whatever such a library.