The real reason WebRTC is important for this site is that it is the first and only way for a browser to communicate in a unreliable method without some (likely slow and unsecure) plugin. See, everywhere else, your browser uses TCP, which, when a packet fails, it will keep resending it until it works or gives up. This is ordinarily very good because it would be bad if random paragraphs or part of some code failed to load and you never even found out that anything was missing. However, this made it basically impossible to test the packet loss of one's connection. If your computer just kept trying until it worked, there would never be any lost packets. Now with WebRTC, I can tell it to just send the packets in the test once and to never retry them. Then I can just see which ones are missing.
Also, thanks to Google for its free STUN server I'm using to help establish connections.