Convergence: Silverlight 3 To Support h.264 Video

Holy mother of all video codecs, Batman! Microsoft announces Silverlight 3 will support h.264. It’s been a pretty good week for Microsoft on the hearts and minds front. First they role out Seinfeld as a pitchman (you had me at Shoe Circus Jerry). The ad was subtle, avoided the obvious Apple references, was utterly devoid of all normal hyperbole evident in recent campaigns (Surface “revolutionizes” the $10K multi-touch coffee table market), and most importantly no obnoxious “aero” translucency was anywhere to be seen (is it just me or is Aero the equivalent of clear plastic pumps).

However, it was the news that Silverlight 3 will support h.264 video and AAC audio that has me ready to sing Kumbaya, kiss the girls in Redmond or become an English soccer hooligan (lots of drinking and a sport I don’t have to pay much attention to…seems grand to me). Now in typical MS fashion they can’t seem to get out of their own way and appear to be pulling a Zoolander and taking credit for the codec’s development.


Self-aggrandizement aside, this is an absolutely huge move by Microsoft and one they should be lauded for. Sure they didn’t get there first (they actually won’t be there for quite some time) and the Flash Player team’s aggressive moves forced their hand, but the end result helps content creators and the industry as a whole out. It’s a move away from vendor lock-in and toward customer empowerment. Microsoft has big plans for Silverlight. They want it to be embedded on a lot of platforms (mobile handsets, consumer electronics, etc.). They don’t have a dominant market position which means they need to leverage existing and future content repositories. It’s a hell of a lot easier to sell customers on RIA platform than it is to sell them on RIA platform + video format, especially when changing video format means re-encoding a large library. Well done Microsoft. Way to connect the dots and make customer needs come first.

Does Chrome Spell The End Of Browser As Platform?

Love the bold UI / workflow approach of Chrome. It also makes complete sense for Google to make a client service play as the gatekeeper to the world’s information, though I’m not without enormous reservations here (too much power and too much control if they ever become the dominant browser). I’m wondering how the web purists crowd will take a potential kill shot to the browser as a platform (next OS) movement from their heretofore champion?


The article is probably referring to the per tab unique memory space and Google may well intend to build a “platform” to push the OS into the background. However, the implied design considerations of the chromeless UI reflects the importance and commitment to targeted experiences and that’s where runtimes like AIR / WPF shine. Google’s got the resources to forgo the RAD platforms, but most of us don’t. Much is changing in the software / platform world, but it should now be pretty clear that the desktop’s not dead yet.

*Update* After glancing through my feed reader for the first time in about 48 hours, I have to apologize for this post. Maybe I need to take some time away from the blogosphere because I’m starting to sound like all the other blowhards out there. ;-(

*Update* Rands may have taken the cake with his Chrome analysis.