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
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
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.
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."
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
~.~
I'm a peripheral visionary.
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.