Gerard,

I am somewhat less optimistic as to the timeframe all these things will happen. It will probably be a lot longer (at least for QUIC in WebRTC, implemented in browsers, and with infrastructure and vendors using it).

Look how long WebRTC 1.0 is taking. I was promised it will get done in 2015.

But the premise is wrong imho.

QuicRTC is coming. 12 months away..

Http3 is getting ratified and it’s QUIC. 8 months away.

So everything is moving to UDP and always encrypted.

So you have dependency on the IS kernel for networking. Take it anywhere. Playing field kevelled..

Telcos will no longer be able to do QOS / traffic shaping or “network / contention management :)”. Flattening the playing field ….

The 5G system policy architects are using quic for backbone Comms.

AV1 is marching forward.
Its is going to level things – bye bye royalty rent seeking.

I do agree that WASM helps. It’s a huge innovation.

But when you combine wasm and webrtc then you don’t need servers ! So huge level playing field because no capex running costs.

Webrtc NV is interesting and am doing some of those.
I think there are a ton more use cases here that will become apparent too as people get into this and be brave and defy the dogma we all fall into over time.

P2P might really really take off

Sean, I guess you should read this: https://blog.usejournal.com/open-source-business-models-considered-harmful-2e697256b1e3

I tend to agree with it.

Chromium and libwebrtc are at best viewable source. If you work at Google you get the fast path to make whatever change you want, if you don’t it is a much steeper slope. There are also plenty of crbugs that are marked private, and other issues you are going to run into.

It is a shame, because it gets the label ‘Open Source’ while other projects that are actually community owned get ignored.

@Philipp Hancke who knows what hasn’t been caught yet.

100% open source is a myth.

Google are allowed to add their own secret sauce as others do. I am guessing the issue starts when Chrome itself is getting “private”/”undocumented” interfaces that only Google can use.

Looks like the 100% opensource rule is gone though, I’ve seen webassembly files delivered with Hangouts Meet which build inside/against WebRTC without being included.