Live data from Hacker News

Google open sourcing voice and video engine for the web

sites.google.com

41–46 of 46 posts

Re: Google open sourcing voice and video engine for the web

#41
post #28
post #11

Earlier quoted context omitted.

Actually, it was very clear. Jobs promised, in no uncertain words, that Apple will make Facetime an open standard. I remember that well, I was quite excited about that. He lied and I'm quite surprised that virtually no one gave Apple the hard time they deserve for lying during a keynote speech. To quote http://en.wikipedia.org/wiki/FaceTime : "Upon the launch of the iPhone 4, Jobs promised that Apple would work in du…

Jobs promised, in no uncertain words Which were what?

Seriously, asking a question gets down voted? No. Asking a simple question seeking confirmation of something, is merely that, a question. It's spurs conversation. Downvotes are not for things you disagree with. They are for comments that detract from the quality of HN. The answers in response answered the question.

Seriously. There should be a way to flag down vote abuse.

Re: Google open sourcing voice and video engine for the web

#42
post #25
post #11

Earlier quoted context omitted.

Actually, it was very clear. Jobs promised, in no uncertain words, that Apple will make Facetime an open standard. I remember that well, I was quite excited about that. He lied and I'm quite surprised that virtually no one gave Apple the hard time they deserve for lying during a keynote speech. To quote http://en.wikipedia.org/wiki/FaceTime : "Upon the launch of the iPhone 4, Jobs promised that Apple would work in du…

Open standard and open source are different things. Having both an open standard and a full stack implementation (BSD-licensed) is ages ahead of just publishing some details about the protocol.

This is misdirection.

Everyone else is on the same page in this conversation. Open standards are the focus here, and that's exactly what hasn't shown up wrt FaceTime.

Re: Google open sourcing voice and video engine for the web

#43
post #25

Earlier quoted context omitted.

Open standard and open source are different things. Having both an open standard and a full stack implementation (BSD-licensed) is ages ahead of just publishing some details about the protocol.

This is misdirection. Everyone else is on the same page in this conversation. Open standards are the focus here, and that's exactly what hasn't shown up wrt FaceTime.

I was just highlighting that Google went above and beyond here. They are actively participating in the IETF realtime web group and have actually released some code. They could have just released some API docs, and some header files and wait for others to build an implementation while they still use their proprietary code.

Something like this happened to AMF format and Adobe. They release some specs, and then people started to implement Flash servers, except the specs sucked and a lot of stuff had to be reverse engineered.

[Warning: PDF document]

http://opensource.adobe.com/wiki/download/attachments/111428...

Re: Google open sourcing voice and video engine for the web

#45
post #43

Earlier quoted context omitted.

This is misdirection. Everyone else is on the same page in this conversation. Open standards are the focus here, and that's exactly what hasn't shown up wrt FaceTime.

I was just highlighting that Google went above and beyond here. They are actively participating in the IETF realtime web group and have actually released some code. They could have just released some API docs, and some header files and wait for others to build an implementation while they still use their proprietary code. Something like this happened to AMF format and Adobe. They release some specs, and then people s…

Apologies. Given the comment you were replying to, I took it to be an attempt to parry the charge that no specs have been released by attempting to frame it as a call for an open source implementation (and therefore Apple would have not broken that promise, since that's not the promise they made).

Re: Google open sourcing voice and video engine for the web

#46
post #18
post #17

Does anyone have any ideas what the timeline for browser support is likely to be? The website currently says they've been working closely with Mozilla and we expect to see WebRTC support in Firefox and Chrome soon! .

I wonder when Safari will get WebRTC support?

Isn't that about survival of the fittest? Why use a browser that don't support shit when there is a few that does. Might work for now, but not in the future.
Post reply on HN