Linked by Wes Bascas on Wed 3rd Jul 2013 11:00 UTC
Mozilla & Gecko clones Over the weekend, the crew at Tom's Hardware was busy testing the recently-released Firefox 22 using the usual bevy of benchmarks. This roundup included Chrome 27, Firefox 22, IE10, and Opera 12, along with the new Chromium-based build of Opera Next (alos known as Opera 15).
Thread beginning with comment 566157
To read all comments associated with this story, please click here.
Member since:

Other than the relative performance of the browsers the thing that hasn't been mentioned on this site or much is WebRTC support which is far more interesting IMHO.

WebRTC with p2p camera and mic connection between browsers is fucking awesome. I have essentially built an open standards version of Skype for my own edification on the new proposed features.

I suggest checking out (not made by me ... wish it was).

Reply Score: 6

sb56637 Member since:

Hey, that's pretty slick. Thanks for the link. I wish it would let me create a standalone account, since I don't use Twitter.

Reply Parent Score: 3

lucas_maximus Member since:

The library that they are using is called "holla.js" and is a library for node.js and is open source.

I've been playing with it but haven't got anything past a proof of concept. Hopefully when they have an IRC channel up I might actually get a bit further with my app.

Reply Parent Score: 3

Lennie Member since:

I think WebRTC has the potential to change the world.

And it's not just for the browser you can make desktop and mobile apps with it too, it's mostly a protocol and there are libraries for it.

Thus it can be used for many, many applications and it's encrypted by default.

Basically it allows for P2P real time communication.

Audio, video and also data. And it's always encrypted.

There is however no signaling (like XMPP or SIP) but this thus also allow it to be really flexible.

On the audio side, the codec it supports, Opus, is new and was designed for changing environments. Part of it was derived from a codec from Skype.

It can also use the same audio codec which is supported by many VoIP systems.

Video codecs is where the issue is at, it's not defined in the standard yet, there are people for patented H.264-like and more free WebM/VP8-like, but it can be worked around. And even if video is problematic it would allow for many, many useful things.

Doing video conferencing with more than 4 people is less than ideal, you'd want to use one or more central servers.

I've seen applications like:
- video chat
- audio chat
- text chat
- screensharing (not just the browser)
- file exchange
- collaborative editing

It can also pierce NAT like Skype or use a relay if it really can't work around NAT. The relay only sees encrypted data.

There are even people working on Push Notification. So you can receive notification of new calls even if your browser or app isn't open.

Some say it's the next best application/protocol of the Internet after the web.

The best thing would be if a protocol similar to VoIP is build on top which connect to a different identity, like your email address.

It could be like VoIP/SIP where everything is mostly interoperable or like not like a lot of the instant messaging systems.

There are 3 big webcompanies involved with WebRTC, Google, Microsoft and Mozilla. Also the Skype team and companies like AT&T and Ericsson

Edited 2013-07-04 13:28 UTC

Reply Parent Score: 3

zima Member since:

There are 3 big webcompanies involved with WebRTC, Google, Microsoft and Mozilla. Also the Skype team and companies like AT&T and Ericsson

Even though Google closed Gtalk/Hangouts from interoperability? And why would MS be involved with the closed Skype?...

Reply Parent Score: 2