Thursday, August 26, 2010

Re: [MISP] wmv export

***This is a MISP Listserv message. Responses are sent to the list by default.***
***For more info about MISP and the listserv, scroll to the bottom of the page***

On Aug 25, 2010, at 8:19 PM, Mark McKee wrote:

> I'll just put this out there. MS, Apple, Adobe, Google and their ilk would rather destroy the world than cooperate...

I agree with you to an extent. It's the same trouble web designers have had since the browser wars of the 90's. I'm tired of it too.

But keep in mind that they are cooperating on some things. For instance, all four of those companies you mention are using Apple's open source HTML rendering engine, WebKit. Google uses it in Chrome, Microsoft uses it in Entourage and Messenger, and Adobe uses it in AIR. And they're all agreed that standards-based rendering is a good thing moving forward (Adobe begrudgingly so, but then, they're the most threatened by it), and are putting development where their mouth is; when IE9 comes out, we'll have the most unified rendering target we've had since, well, since before there was IE.

Just try to balance the frustration in the competing format space with the realization that SOMEONE has to upset the status quo or we're going to be stuck with the same technologies indefinitely. Yes, Steve Jobs is taking potshots at Flash, but then, I don't want to still be using Flash to deliver video in 2020, either - do you? Delivering video through an HTML5 video tag based on a known standard is far preferable to having to rely on a closed-source plugin; it's what us web developers have been wanting for a long time, and paves the way for a more semantic web. Yeah, it makes me change my video production process, but once I get out of a closed system, I can migrate my video to whatever's next more easily, and I'm less likely to have to. It's change, but it's GOOD change.

In this light, this might make everyone feel a little better:


The H.264 group have declared that use of H.264 is free to use for life, instead of expiring in 2015. Presumably, this is aimed directly at making a compromise so that Firefox will come on board (allowing HTML5 to have a single video codec across all major browsers) and video producers won't have to worry about encoding to H.264.



To leave the list, please email us at:
For other list info, please visit:
Available in RSS:

No comments: