Microsoft Going Its Own Way On Audio/Video Specification
An anonymous reader writes "Several groups are currently working on specifications for plugin-free, real-time audio and video communication. The World Wide Web Consortium has one called WebRTC, rudimentary support for which is found in Chrome, Firefox, and Opera. Back in August, Microsoft announced its own specification, CU-RTC-Web, because it thought WebRTC wasn't worthwhile. W3C carried out a vote to choose between the two specs, which came out strongly in favor of WebRTC. Microsoft went ahead anyway, and it has now published a prototype for the proposed specification. 'So what's Microsoft playing at, persevering with its own spec in spite of its rejection by the WebRTC group? The company's argument is twofold. First, WebRTC simply isn't complete yet, and Microsoft believes that working on its proposal can shed light on how to solve certain problems such as handling changes in network bandwidth or keeping cellular and Wi-Fi connections open in parallel to allow easy failover from one to the other. Even if Redmond's spec isn't adopted wholesale, portions of it may still be useful. Second, the company believes that WebRTC may not be as close to real standardization as its proponents might argue.'"
And something with learning new tricks
You've lost the mobile war, you've lost the browser war and you're going to lose the OS war soon enough.
No one use IE any more.
Mod me down, my New Earth Global Warmingist friends!
Chrome also supports the standard and can already interface with IE 10. WebRTC is not standardized as no one can agree on the exact implementation yet and no 2 browsers can work with it the same. Microsoft did submit this to the W3C with its implementation.
Perhaps someone more knowledgeable can care to comment?
Due to Microsofts past with IE 6 and also them buying Skype I do feel a little skeptical. Is WebRTC really that difficult compred to the other one?
http://saveie6.com/
Are we supposed to be surprised by this?
Does anybody even care what Microsoft does these days? They even seem to fail at being evil, though they still try.
When all you have is a hammer, every problem starts to look like a thumb.
Hasn't MS always went its own way regarding standards and specifications?
Microsoft has followed this path from the beginning with standards: Adopt, adapt, expand and control.
Always adding something "extra" so that other software that actually follows the standard doesn't work quite right with stuff built to Microsoft's "standard" so that the stuff built to actually follow the world standard looks inferior. :(
--Tomas
This is pretty crazy...
Microsoft owns Skype. Skype's technology is half of the Opus codec. Opus is what WebRTC is supposed to use. So why isn't Microsoft all over this?
I'm thinking the one where they make a new standard to unify the 15 older ones. I'm on my phone, please link.
FU-RTC-Web
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Microsoft no longer have "big bear" status and you don't need to play according MS rules anymore.
* Anything but FLAC and Codec2 (because FLAC doesn't compress and Codec2 is voice-only and ultra-low-bandwidth).
Bruce Perens.
the company will make sure that WebRTC may not be as close to real standardization as its proponents might argue.
There, fixed it for you.
http://xkcd.com/927/
As it stands, WebRTC sucks. I was hoping to utilise it in a current R&D project, but even FF and Chrome have different implementations of it to the extent tha it fails at what it's supposed to do. As such, it's in danger of becoming another mutant web standard that simply isn't, just like HTML5 video...
So have you not been paying attention for the last 20 years or what?
Same shit as usual. corrupt a standard, roll it into the os until it becomes the new standard.
"We think their standard is crap, so let's make our own"
"But, how will it work?"
"Lots of security holes. compatible with IE only, and make damn well sure that they can't remove it from the OS."
Great job, Microsoft, add another junk program that takes up our precious CPU.
~.~
I'm a peripheral visionary.
Please note that I did say Write to the Standard.
MS handles the standard just as well as any other browser.
That means nothing as to how a site works though, you can "write to standards" all day long, but it's very easy to misunderstand a standard, or to simply have bugs that only surface on one browser because THEY misunderstood standards. You still have to test even when "writing to standards".
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Now not only will we have separate internets for each country, so governments can decide what their people can see, but each company will have it's own proprietary browsers for their particular chunk of the internet. That is absolutely stupid, classic Microsoft! Can we change the name Steve to Wrong Way Ballmer since he keeps going the opposite direction as everyone else, invariably to Microsoft's chagrin?
Chrome and IE 10 interact fine if you follow the link.
Yes, we can bash MS for being evil but the grandparent is right. It is an empty standard with no implementation and is a nightmare as a result.
If Mozilla supports it then we will use that. Netscape and IE supported non w3c standards back in the day aka quirks mode even though they did do things only each browser would do.
It looks like we might have another modern quirkmode in this if everyone supports it.
http://saveie6.com/
In the post Flash era we are taking HUGE steps back. In-browser support for Video Codecs are neither here nor there, where we quite literally have to encode to two or even three standards. But, at least we have Wowza that can stream to various standards and Codecs. Audio is no better, with Google and Apple are using the Web Audio API while Firefox is committed to the Audio Data API, which has NOTHING in common with the Webkit standard. And the built in audio player on the Android Browser? WHAT. A. FUCKING. JOKE. And of course Apple's "HTTP Live Streaming" is NOT at all suited for actual Live Streaming. The latency is terrible!
And then we have Real Time Communication, an area that Flash excelled at with and RTMP and AMF, as well as various servers such as FMS, Wowza and SmartFox capable of facilitating chat rooms, multi-player games, even MMORPGs.
Getting data and devices streaming FROM THE BROWSER just isn't there. The support is incomplete, undecided and very much in flux. We are quite literally still a few years out from a standard and usable platform across browsers. And now we have Microsoft wading in to offer what will surely be a typical Proprietary Solution only available to Microsoft Partners and Licensees.
Frankly, this rush to kill Flash has been a self-centered money grab to try to take away the video market from Adobe and HAS FUCKED the users, leaving them with a broken internet and competing standards.
The hype of HTML5 has been years coming, with Steve Jobs and legions of techies on slashdot and other sites calling for the death of Flash.
Yet here we are, years out and we don't have anywhere near what we had with Multi-Media and Real Time Communication in 2005 with Flash.
How anyone can sit here and look at the current state of affairs and not see it as a monumental clusterfuck that is HOLDING BACK the progress and innovation we were promised with HTML5 is beyond me.
How about the REAL reason Microsoft went their own way?
Because they want to control the plan form so that if they successfully gain traction, they can start locking everyone else out. Just like they do with everything else.
WebRTC isn't just for browsers, but ATAs is well.
Shai Schticks:"You don't make peace with friends, you make peace with enemies"
Of course they are going to create their own standard.....
More like
"We can't make a good product so how can we make other companies products appear to be bad"
"Let subvert the standard, create a shadow standard that's similar and incompatible and force it onto people with Windows"
Trouble is, the Windows franchise is in trouble, the most popular OS now is Android and its more important what Webkit supports than what IE supports.
Why should *any* codec at all be built in?
Make them ALL plugins. For really popular formats, just ship the plugin with the browser by default. Browsers are bloated enough as they are - trim the binary down to the minimum possible, and only load the plugins when they are needed. This also forces the browser developer to optimize the codec plugin path well enough to stream live video, instead of optimizing the builtins and leaving the plugin ones with half-baked support.
It would also allow users to remove support for formats they don't like/want/need. Apple fans could delete everything except aac, Microsofties could delete everything except their own. RMS could delete all the non-'Free' ones.
said no one, ever.
"How anyone can sit here and look at the current state of affairs and not see it as a monumental clusterfuck that is HOLDING BACK the progress and innovation we were promised with HTML5 is beyond me."
If you're going to rant about taking a huge step backward, look no further than media streaming. Media streaming, where every time you want to watch the SAME video you have to download it again, wastes bandwidth, a much more precious resource than the 32GB micro-SD card you slip into your smartphone, much less the 3TB hard disk in your PC.
You're right though about "vested" interests preventing the progress of technology, from energy production to file sharing to medicine.
Microsoft submitted Vector Markup Language to the W3C. The standard that came out was SVG with SMIL integration.
Not only did Microsoft not implement SVG in IE6 at that point, they came out with a bastardised version of SMIL called "HTML + Time". Remember that? How well did that go? That's right, every other browser now has SMIL integrated SVG except IE.
You mean to say that Microsoft is not adopting an existing specification but designing it's own proprietary one? Get outta here! I don't believe it!
Like they haven't done that before. :P
Codifex Maximus ~ In search of... a shorter sig.
If not, how about Betamax?
Oh come now! If you really want a standard to take hold, you'll need a much catchier name..
How about, "Plays For Sure II: This time we really mean it!*
* until some soon to be announced EOL date.
Javascript, cookies, flash, and ActiveX must be enabled in order to view this sig.
The Web is DEAD to me as a dev target. It's shit like this that just re-affirms my decision to NEVER write another web app again.
Wake up people! All we're doing is slowly turning HTML+CSS+JS into something EVEN SHITTIER and SLOWER than Java.
Every mother-fucking web-site, even this one -- hell even literal mother-fucking sites like redtube -- are WEB APPLICATIONS. It fucking SUCKS to make a web app. Now that cross platform application development toolchains exist I can build my application as beautiful clients for Windows, OSX, Linux, Androd and iOS, and it will take LESS TIME than writing the same thing as a web app.
Long like the Internet, but FUCK THE WEB.
It's been over half the life of the damn Internet and we're still stuck on HTML 4.01! FFFFFFUUUUUUUUUUUUUUUUCK IT!
And with the 11th bride walks up to the altar, you got to wonder just how stupid she really is. Many a MS apologists is really just suffering from battered wife syndrome "nobody understands him, he will chance, he told me!".
Sad. Although I find it a useful measurement to see if a person is worth taking notice off.
For instance "Sponge Bath" and "DavidClarkeHR" can be filed under the heading, to stupid to live. It ain't a nice thing to do but god does it save time and I rather be filed under nasty then stupid.
MMO Quests are like orgasms:
You may solo them, I prefer them in a group.
So MS will be publishing their own standard. What will happen?
.wav file format is a good example of this; it's pretty much always supported. That doesn't mean it's not brain-dead (Why on earth is the length of a WAV file a SIGNED integer?)
1. Looking at VBscript and Silverlight/Moonlight, it will essentially fail - alternatives exist (Javascript, Flash) that are equally viable and more widely supported.
2. Some idiots will use MS-only tech ANYWAY, breaking support for anything but the Windows platform and alienating a substantial user base.
3. If the spec is open (looking at dot net), some open source group will produce their own version to permit interoperability with other platforms.
Wasn't it netflix that required Silverlight to be installed?
4. However, this doesn't guarantee that code written for Windows-based products will actually work out of the box on the other platforms.
An example of this once again is dotnet: Even with the whole CLR available on Linux, some idiot will tie their source code into a proprietary Windows API, e.g. to have SharePoint interoperability.
5. Eventually (looking at CSS and MS' implementation of JavaScript and the document object model) MS will have to give in and better support the actual official standard, but by that time the damage will have been done. Remember the original HTML spec only permitted writing JavaScript in the HTML header - just think for a moment how many cross-site-scripting issues that prevents. But NOOO, MS decided people should be allowed to litter script tags all over the document body. Great going, MS.
6. In some cases, an MS spec will end up sufficiently well-documented that it becomes the de-facto norm across platforms. The
Anyway, I'm not exactly looking forward to the implications.
Visit http://ringbreak.dnd.utwente.nl/~mrjb/growingbettersoftware to download your free copy of the book
connection? I think so.
Be seeing you...
Microsoft still insists that they want to work on their own project, but why not contribute that effort to a working group whose goal is to improve WebRCT, or even help steer the project away from the SDP dependance that they so loathe?
Also, if they do continue down the loner's path, will they also be an ass, patent a whole bunch of core mechanisms, and thus greatly hinder WebRCT from becoming complete?
-- "Simplicity is prerequisite for reliability." --Dijkstra
If MS hadn't mucked around with their own version of HTML, we wouldn't have to put up with all that AJAX crap like google maps.
Remember the mp3 vs mp4 debate? It was so much better they ran with it.
How did that pan out? No one wants to see microsoft win any format war.
In fact it is the opposite and microsoft doesn't want to admit defeat.
But go ahead and tell us what we are doing wrong MSN so we can fix it ourselves.
enough said
So what (in the sphincter O Hell) is Microsoft playing at...
Ease up a bit Captain, goin' on three years now and Microsoft ain't had nothin' twixt her nethers weren't run on batteries!"