3 ms·
A lot of people here are arguing that "Microsoft has legitimate concerns". Of course MS are framing it like that - would you really expect them to say "We made
by beagle3 14y ago
A lot of people here are arguing that "Microsoft has legitimate concerns". Of course MS are framing it like that - would you really expect them to say "We made this proposal because Google+Firefox+Apple are neutering our Embrace+Extend+Extinguish ritual, and additionally the WebRTC thing is going to demolish the $8B value of our skype purchase"?
The fact that they may have good technical arguments should not confuse you. They're not doing anything to make the web better. They are doing everything to make Microsoft's hold in the market stronger. Everything else is incidental.
Story time:
Back in 1999, I worked on instant messaging infrastructure, and as a result followed the related IETF workgroup closely. That workgroup had very interesting discussions that went absolutely nowhere over a few years. At some point, everyone threw their hands up in the air and adopted XMPP - not because it was good (far from it, compared to other suggestions that were made) - but because an implementation was made and progressing, and becoming a de-facto standard.
What I realized through 1999-2002 following the standardization process was that, although every single argument ever made was of a technical nature, it was a game played between AOL, MS, Netscape and the other members of the workgroup, the game being "either you guys accept my existing infrastructure and give me dominance, or I'm not sharing my toys". And since no one gave up, toys -- to this day -- are not shared, and IM networks are still mostly disjoint.
The WebRTC game might be more delicate, but the validity of the technical arguments (which was there in the IM discussions too) should not confuse you. It's about market control and dominance, not about technical excellence.
- Camillo 14y agoSure, but are the other players completely disinterested? Some of them might have pure motives: take Mozilla, for instance, which seems to see WebRTC as a trojan horse to force the market to adopt non-MPEG codecs. They have the users' best interests in mind, but it's not obvious that their focus on that aspect necessarily yields the best web RTC standard.
- beagle3 14y ago> but it's not obvious that their focus on that aspect necessarily yields the best web RTC standard. Best RTC standard for who? I believe that patent-free RTC (as WebRTC provides by virtue of preferring WebM) is better than a patent-encumbered even if it has a slightly better session initiation/description protocol. Regardless - yes, one should definitely try to map the underlying reasons and subtext of every statement. But the bottom line is: Google has been working, in public and with a freely usable implementation, on a specification. Mozilla adopts same specification (and mostly same codebase). Said specification ALREADY works on iphones, android phones, Chrome, Firefox and even IE (with the right plugin). Microsoft proposes something, not completely defined, only provides a plugin implementation, only for IE and Chrome, unsupported on any phone. In my book, it needs a much better story than just "better session descriptor". And frankly, with Microsoft's past of hijacking the web standards, the office openxml iso process hijacking, all the linux patent threats and the android patent extortion that is STILL ongoing, they need to work much, much, harder before I even give them the benefit of a doubt.
- ZeroGravitas 14y agoThere seems to be widespread confusion about WebRTC already adopting VP8/Webm as a mandatory-to-implement codec. No such decision has been made. Though the two furthest along implementations (Chrome and Firefox), which also happen to have about a billion users between them are both pushing VP8 which might make it a defacto standard anyway. They (IETF WebRTC) have adopted the Opus audio codec as mandatory-to-implement, which isn't officially part of WebM (though apparently Chrome 25 can play it in that container) as it's far more suited to real-time communication than Vorbis. For the video codec, they were going to call for consensus (basically on VP8 vs H.264) but Google mysteriously suggested that the decision be delayed on the day before it was supposed to have happened, claiming to have something in the works that would solve the whole problem to everyone's satisfaction. My wild guess (given the fact that the VP9 encoder and decoder is now available to download from mainline codebase and is beating x264 and H.265 objectively and subjectively [1] for pre-recorded content--and I'd maybe guess that even VP8 beats H.264 for standard WebRTC use cases) is that they're working out some behind the scenes political deal with other industry partners to jump straight to VP9, either by getting all relevant parties on board regardless of patent sabre-rattling, or by working something out with patent holders to neutralise that threat. Both are a bit wild as I said, the more boring explanation is that Google feared losing the call for consensus and had something brewing to sway a few swing voters but didn't have it ready in time. [1]: http://forum.doom9.org/showthread.php?p=1611395#post1611395 http://forum.doom9.org/showthread.php?p=1611395#post1611395
- ZeroGravitas 14y agoWebRTC is being develop by IETF and W3C both of whom have very strong preferences for royalty-free (and otherwise RAND-Z/RF) standards. Why would you imagine they would pick an MPEG codec? Maybe the low-delay wideband voice and audio codec also developed by IETF under the same requirements (both technical and royalty-wise) would fit better? And, on the topic at hand, have Microsoft made any public statement about their support for that codec, despite the fact that it was co-developed by their Skype purchase? Only vague murmurings that the alternative standard discussed here shouldn't be "tied to a single codec". Note the masterful misdirection that would make you thing that WebRTC was "tied to a single codec" when in fact you can use any codec you like, you just have to support Opus (best in class, yet RF) and G.711 (old and busted for legacy interop) to help ensure interoperability. The fact that the simple logic of this seems somehow underhand to you is a testament to the great political job that Microsoft, Apple, Nokia and others have done in the web codec arena where a codec, which could never be adopted under W3C rules, has come to seem like the obvious choice when really it was a bold attempt to subvert the W3C into not specifying a royalty-free codec so that a royalty-encumbered de-facto standard of their choice would fill the gap that was left.
- yajoe 14y agoYou are spot on. I was at Microsoft during one of these protocol discussions. I worked on a popular (and contentious) directory product for whom interoperability (or lack thereof) was the product's bread and butter. For the mid-2000 release we were embracing XML goodness from the W3C. XML was in style in the same way JSON is today. We settled on WS-Transfer and IBM's WS-ResourceTransfer extensions because, frankly, it didn't matter what we picked so long as it was XML. Well, we worked on the release for 2 years and then 6 months before shipping our VP decides that decision posed too big of a risk for IBM gaining 'the upper hand.' He made a point of blaming people for the decision he had approved years ago. We then had to rip out a perfectly good and tested implementation of WS-ResourceTransfer, design a replacement, make it an industry standard, and finish with the original schedule. We came up with something 'different' called MS-WSTIM ( http://msdn.microsoft.com/en-us/library/dd302851.aspx http://msdn.microsoft.com/en-us/library/dd302851.aspx -- fun fact, I got stuck writing most of those docs). After the change our principal technical architect spent the next year going to conferences talking about the technical merits of how MS-WSTIM exceeds WS-ResourceTransfer in oh-so-many ways. He supposedly worked to convince minor players to adopt the new 'industry standard.' The whole thing was a sham. MS-WSTIM is WS-ResourceTransfer by a different name. It just wasn't IBM's, and like so much at Microsoft, politics reigned supreme. I would be surprised if the same were not happening here.