Google Adds Hardware Acceleration Support to WebM
Replying to: Mass hypocricy by justfinethanku
You can also add h.264 support to a Chrome browser by downloading the plugin. They're just removing it from default support. This part is smart. There is NO WAY that a format that will cost producers a TON of money should become the "standard" for HTML5 video development. That's like saying that Flash should become the standard for HTML5 advertisements. One of the POINTS of HTML5 is to move away from that "if you use this, you'll have to pay us" ****.
WebM is also free for developers to use. h.264 isn't. That's the advantage. It's not just in certain instances, it's EVERY TIME the person using the codec is making money. This means that unless you're running an ad free, non-profit website, you technically need to pay them royalties.
On top of that, it's only free through 2016, at which point their policies will be "Reviewed"
I dont agree with how Google went about it either, but people are taking this the wrong way. They're trying to justify h.264 as a WEB standard by saying that proprietary NON WEB formats use it. Who give a f**k what they use?
Oh, here is the webM source code: http://www.webmproject.org/code/
It's too late for them to do anything about Flash, or AAC, or MP3 because those are all adopted standards. Video IS NOT standard yet just because 2 mobile platforms (one of which is android) currently support it, as does ONE major browser (safari). This means that there's still a chance that some other format, be it webM or Ogg Theora, or something else could become the standard.
The change was poorly executed (and so were the reasonings) but that doesn't mean this wasn't a good move.
No replies to this message