Comments on: Top 5 Excuses for NOT Adopting WebRTC (and Why They Make no Sense) https://bloggeek.me/excuses-not-adopting-webrtc/ The leading authority on WebRTC Sat, 28 Dec 2019 15:14:44 +0000 hourly 1 By: Alexandre Ballesté https://bloggeek.me/excuses-not-adopting-webrtc/#comment-117698 Sun, 12 Oct 2014 18:57:25 +0000 http://bloggeek.me/?p=9024#comment-117698 In reply to Tsahi Levent-Levi.

Yes, it’s not in their web page, you have to dive deeper to find it.

We implemented for the portal chat that Sakai already included.
Students and teachers can now talk with any of their University connections using WebRTC.

Here are the presentation I did for the S2U Conference in Madrid ’13 where I got that question:

https://docs.google.com/presentation/d/1vMa3EHQBkAP9eOxXrAPW9NZNE4sW9Q_DOzERcnQy8mw/edit?usp=sharing

Implementing WebRTC for Sakai made me to fall in love with WebRTC and started with another guy a opensource webconference platform based on that technology. (loowid.com)

]]>
By: Tsahi Levent-Levi https://bloggeek.me/excuses-not-adopting-webrtc/#comment-117697 Sun, 12 Oct 2014 17:55:31 +0000 http://bloggeek.me/?p=9024#comment-117697 In reply to Alexandre Ballesté.

Thanks Alexandre.

So Sakai LMS uses WebRTC these days? It isn’t apparent at all from the website.

]]>
By: Alexandre Ballesté https://bloggeek.me/excuses-not-adopting-webrtc/#comment-117696 Sun, 12 Oct 2014 17:26:33 +0000 http://bloggeek.me/?p=9024#comment-117696 Agree with the post. Specially I liked the ios one. Some argued to me this pretext when I was presenting an implementation of webrtc to Sakai LMS, and I answered wit the same response. “Good luck with flash.”

]]>
By: Tsahi Levent-Levi https://bloggeek.me/excuses-not-adopting-webrtc/#comment-117695 Mon, 06 Oct 2014 17:39:08 +0000 http://bloggeek.me/?p=9024#comment-117695 In reply to Art Matsak.

Art,

Saw that announcement on your blog already 🙂 keep up the work you’re doing @ Gruveo.

]]>
By: Tsahi Levent-Levi https://bloggeek.me/excuses-not-adopting-webrtc/#comment-117694 Mon, 06 Oct 2014 17:38:24 +0000 http://bloggeek.me/?p=9024#comment-117694 In reply to Andy Abramson.

Andy, that is correct.

The interesting story about Vonage is that they started when WebRTC had abysmal support for iOS, and they still found it the easiest path to VoIP on mobile.

Vendors taking that route today have considerably easier work in front of them with WebRTC.

]]>
By: Art Matsak https://bloggeek.me/excuses-not-adopting-webrtc/#comment-117693 Mon, 06 Oct 2014 17:36:08 +0000 http://bloggeek.me/?p=9024#comment-117693 Thank you for mentioning Gruveo, Tsahi. We are actually launching our iOS app next week, and that probably wouldn’t happen without us switching to WebRTC!

]]>
By: Andy Abramson https://bloggeek.me/excuses-not-adopting-webrtc/#comment-117692 Mon, 06 Oct 2014 15:07:27 +0000 http://bloggeek.me/?p=9024#comment-117692 Great post and thank you for bringing clarity to so many who simply “don’t get it.”

Already Vonage (amongst others) has embedded WebRTC into their iOS client so I don’t see that as a hurdle, vs. development time and interest.

]]>
By: Tsahi Levent-Levi https://bloggeek.me/excuses-not-adopting-webrtc/#comment-117691 Mon, 06 Oct 2014 09:52:58 +0000 http://bloggeek.me/?p=9024#comment-117691 In reply to Lennie.

Lennie – thanks for pointing that one out.

]]>
By: Lennie https://bloggeek.me/excuses-not-adopting-webrtc/#comment-117690 Mon, 06 Oct 2014 09:38:52 +0000 http://bloggeek.me/?p=9024#comment-117690 On point 5/standardization:

Many are probably from the telecom industry and don’t understand how Internet standards from W3C or IETF work. IETF has a motto: rough consensus and running code.

The W3C or IETF first creates drafts, the vendors start creating code for the things that won’t change in the drafts while they are being written. So a couple of vendors put it out in the field and only after it works as expected will it be standardized.

So if you think it matters that it isn’t a standard yet: it does NOT.

]]>