3 ms·
This would actually be a complete regression. I mean, what's the difference to you between Flash Player streamed per-page and Flash Player preinstalled and sand
by astrange 12y ago
This would actually be a complete regression. I mean, what's the difference to you between Flash Player streamed per-page and Flash Player preinstalled and sandboxed?
And a custom codec would just be a browser plugin, only in bytecode.
What gives native playback its power and fan noise advantage over Flash is ASIC-based hardware decoding, which is difficult to customize. Though I'd be interested to see the battery life you get playing video in a loop with libavcodec compiled to JS...
- unwind 12y agoHow about a JavaScript-to-FPGA transpiler? :) Go grab a Zynq eval board (http://www.xilinx.com/products/boards-and-kits/EK-Z7-ZC702-G.htm http://www.xilinx.com/products/boards-and-kits/EK-Z7-ZC702-G...) and implement that, we'll stick around! :) In all seriousness, that would be really really cool. Especially if FPGA blocks become more common in general purpose/desktop processors. It should be possible to design some kind of signal-processing API/framework in JS that lends itself to FPGA synthesis behind the scenes, right?
- nl 12y agoIn theory a WebCL based codec could utilize hardware too.