4 ms·

Couldn't a software decoder be written in Javascript/HTML5? Then no plugin needed - which also means Metro mode support - and it should be passable for most des

Couldn't a software decoder be written in Javascript/HTML5? Then no plugin needed - which also means Metro mode support - and it should be passable for most desktops. And if it is choppy then hey, Chrome has built-in support...

buster 13y ago
A laptop becoming noisy and a webpage that will suddenly become unresponsive? Who is his right mind would implement this on his own webpage? It would only be attributed to your "shitty, slow" site, users don't care what video codec their browser supports.. That said, i had so high hopes for ONE standardized video codec in HTML5, but the w3c/whatwg just fucked it up (or better yet MS, Apple and Co. who couldn't agree on one standard just for profit-reasons).
- harrytuttle 13y ago
  Spot on. This is the usual endgame for design by committee unfortunately especially when all the players are purely self interested. Someone needs to say: product X or fuck off.
- meepmorp 13y ago
  > or better yet MS, Apple and Co. who couldn't agree on one standard just for profit-reasons Odd that the two companies you explicitly mention were just fine using h264 and didn't really stand to make money off the decision.
  - ZeroGravitas 13y ago
    Actually Apple was on record as being against patented tech in W3C standards and reached reportedly reached out to the patent holders to see if they would licence H.264 baseline royalty free and they refused. Apple also once held up the release of a new version of QuickTime until the Mpeg-LA backed down from the crazy royalty structure they planned for AAC. But they failed this time, so Apple supporters pretend everything is fine with the current royalty system, and Apple opponents pretend they never even tried.
keeperofdakeys 13y ago
Video decoding is one of the things you really don't want to run in javascript (although it has been done). Besides a lack of ints, you have no access to SSE and other speedups. This is exactly the kind of thing that nativeclient would be good for, however.

buster 13y ago

A laptop becoming noisy and a webpage that will suddenly become unresponsive? Who is his right mind would implement this on his own webpage? It would only be attributed to your "shitty, slow" site, users don't care what video codec their browser supports.. That said, i had so high hopes for ONE standardized video codec in HTML5, but the w3c/whatwg just fucked it up (or better yet MS, Apple and Co. who couldn't agree on one standard just for profit-reasons).

harrytuttle 13y ago
Spot on. This is the usual endgame for design by committee unfortunately especially when all the players are purely self interested. Someone needs to say: product X or fuck off.
meepmorp 13y ago
> or better yet MS, Apple and Co. who couldn't agree on one standard just for profit-reasons Odd that the two companies you explicitly mention were just fine using h264 and didn't really stand to make money off the decision.
- ZeroGravitas 13y ago
  Actually Apple was on record as being against patented tech in W3C standards and reached reportedly reached out to the patent holders to see if they would licence H.264 baseline royalty free and they refused. Apple also once held up the release of a new version of QuickTime until the Mpeg-LA backed down from the crazy royalty structure they planned for AAC. But they failed this time, so Apple supporters pretend everything is fine with the current royalty system, and Apple opponents pretend they never even tried.

keeperofdakeys 13y ago

Video decoding is one of the things you really don't want to run in javascript (although it has been done). Besides a lack of ints, you have no access to SSE and other speedups. This is exactly the kind of thing that nativeclient would be good for, however.