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
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.
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?
No one use IE any more.
Sure they do. They don't have the majority numbers they used to have back in the old Netscape days, but they still have market share. Any web developer worth their salt will at least use IE for testing purposes (if you're developing websites, not testing in IE for whatever reason, then you suck as a developer). I also know several people personally who use IE because it's what they're used to, and they're not power users (they have difficulty learning unfamiliar programs on their own). Even after I've spoken to them and advocated the use of Firefox (or of late, I'd advocate Chrome), they chose to continue using IE.
I'm not saying that IE is the best browser out there (although they have made great strides in standards compliance and security since the days of IE6), but to state "no one uses IE anymore" with no facts to back it up is simply short-sighted and borderline zealous.
FC Closer
FU-RTC-Web
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Any web developer worth their salt will at least use IE for testing purposes
If you write to the standards you don't need to test in IE any more than any other browser.
If IE can't handle standard code, its somebody else's problem.
Sig Battery depleted. Reverting to safe mode.
* 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.
No one use IE any more.
Except there are many corporate intranets that are IE only. Hell, I've seen SharePoint 2010 instances that don't even play well with IE 9...
Here you go: comic
If IE can't handle standard code, its somebody else's problem.
Spoken like a man without clients/customers...
"Convictions are more dangerous enemies of truth than lies."
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...
If IE can't handle standard code, its somebody else's problem.
It is your problem when someone using IE browses your website and the site doesn't look or work well.
Who are they going to think is an idiot, you or Microsoft? After all, most other sites they browse work fine in IE...
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Please note that I did say Write to the Standard.
MS handles the standard just as well as any other browser.
Sig Battery depleted. Reverting to safe mode.
"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.
Many websites have stopped supporting older versions of IE
Mendacem Memorem Esse Oportet
~.~
I'm a peripheral visionary.
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.
You don't get out much. While it doesn't have the market share it once did a lot of organizations/companies still use it as their standard browser. It also isn't all that bad these days. I use all three major browsers but tend to use Chrome more than others, but IE is not going away any time soon.
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?
I had FIrefox work just fine with Sharepoint 2010.
It makes me wonder how complex is sharepoint and what does it actually do? If you need a consultant to set it up and programmers to fiddle with it then of course teh guys at work only know IE7 and IE 8 would write the vbscript.
The ones I got to work were compliant and I sincerely hope it is not as complex as I mentioned above as this was Microsofts answer to wikipedia. It should be simple theoretically with templates right?
http://saveie6.com/
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.
Even if you were right (and you are not) many people consider "writing to the standards" to mean "it works in Chrome and Firefox" and this is definitely not what it means.
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"
Go launch IE 6 and try to use it? That is my cite.
On VMWare IE 6 crashes on the default MSN news page within 30 seconds. Pretty bad if you ask me since MS makes it and even www.microsoft.com doesn't work properly in IE 6 anymore.
The rule I use is 5%. If you spend 50% of your time with 5% of the market it is time to ignore them and put a polite banner with links to later browsers asking them to upgrade to enjoy the latest features.
You need to draw the line somewhere and 40% to 50% of all customers who use IE 9/10 who do not support this standard is batshit crazy! IE 6 is another matter. IE 7 is going out of support too as it approaches the 5% number too.
http://saveie6.com/
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.
Ours. We only support IE 9+, any older and we'll send you Chrome Frame so we don't have have to worry about the stupidness that is IE 7/8.
If you write to the standards you don't need to test in IE any more than any other browser.
Clients don't care if a site is standards-compliant, they care if their potential customers will look at their site and see a hot mess. If you can give them something attractive and standards-compliant, so much the better.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
"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.
Which site is that if you do not mind asking?
IE 8 seems a little earlier. Especially if you have business users. Even on the internet many sites still work better with IE 8 including Slashdot. Yes, they have standards, but when they see a string that says IE they feed old IE code.
Maybe slashdot.org can fix the comment threading in IE 9?
http://saveie6.com/
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.
If you write to the standards you don't need to test in IE any more than any other browser.
Clients don't care if a site is standards-compliant, they care if their potential customers will look at their site and see a hot mess. If you can give them something attractive and standards-compliant, so much the better.
They do care if one delivers a site that isn't 100% in IE, however (or any other browser for that matter). That's why I don't get the mentality of those who actively block IE just for being IE. I remember a site a few years back that had loads of info about the 6581 SID chip, and what struck me as odd was that it actively blocked IE users. Now, at the time, that could reasonably be explained by saying "IE isn't standards compliant", but nowadays that argument doesn't hold much water with me. Even though I use Chrome primarily at the moment, if I find out that a site actively blocks any standards compliant version of IE, I will refuse to visit that site even though I don't use IE for daily browsing. Code to the standards, test in all major browsers (or at least all major rendering engines, I personally test under Trident, Gecko, and Webkit - including Safari on Windows, to get an idea of how the site will render on Safari for Mac, even though I know the font rendering is slightly different and not quite as good as on a Mac), and fix your bugs. Simple as that.
FC Closer
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
This what's great about only having a vanity site, I just code to the standard and test in Firefox :)
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
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!"
While I agree with your sentiment, this is not really true in the Real World (tm).
My philosophy, as a webdev of...8 or 9 years now... is that you should test in IE so that the IE user experience is passable / acceptable. IE users should be able to access your site and not see a broken site. It can be degraded; it can even automatically redirect them to a page that says "your browser is so old and busted we can't show you our new hotness -- go upgrade, biatch."
There are 2 main reasons for this:
The sites I work with are pretty progressive about their IE support and are willing to only support back to IE8 (or in one case, IE7), so IE6 is no longer a concern. It's fine to advocate using better browsers, and it's even fine to design your site to the W3C specs explicitly (eg. go for the gold with your CSS and HTML5), but you should always test and at least provide your IE users (however many they are) with a degraded, yet stable, experience, at least. Base it on your analytics data.