Check here: https://en.wikipedia.org/wiki/VP9

Not sure which ones are also used by Chrome. discuss-webrtc might be a good place to pose this question.

I’m the Olivier who wrote that question on the Webrtc-group :-). Thank you for sharing that point.

Globally, I’m a huge fan of WebRTC, I develop web applications with that technology since 2012/13. But when I discovered mobile applications, I was a little bit lost.

My remark was more on giving to mobile developers the right information to succeed. Once on production with tons of users, how do you decide to update your WebRTC stack ?

Is there a risk ? Do I need to pass a complete no-regression campaign ? Is-it still compliant with my Web application, my gateway, my conference server ? And is there adaptation to my code to do ? All that tests have a cost (time, people…).

I just want to illustrate that the release notes are the only documents we have as developers to understand what to do without having to dig into the source code.

Your explanations and the ones given by Alexandre and Philipp helped me to see the full picture.

Thank you,
Olivier

Lauro, thanks for sharing.

The challenge with the current set of experiments is that they are leashed on running services without any knowledge about them. It isn’t about trying to add a faster web (SPDY and QUIC), where Google simply added a brand new layer of transport and experimented it in front of their own services. It is about small changes and tweaks made to improve and optimize performance that are tested on third party services at large without their awareness. I understand the need to run these experiments, but I am not sure the way they are conducted is the best one.

As for the rest, I definitely agree.

Complain from Google for “experimentation”, I don’t think so. In the last decade the web has gained many APIs from which Google or its contributors kicked off and continued to bet and experiment even if other players wrinkled their nose … and most of them followed them.

When I look at the discussion mailing lists or the most high-profile issues on GitHub, I see that the circle of those closest to following directions is very narrow and yes, I see few participants from other teams in the game.

I believe WebRTC will follow the next few years with no surprises, but it’s hard to keep high expectations when you don’t know what key stakeholders think for its future.

I also think that more than thinking about what we can get from WebRTC today is what we want to have from it for the near future, what do developers and entrepreneurs expect of this technology in specifying (and implementing) for years to come?

Thanks for this Sean. I think we are in agreement.

Especially in the less complaining and more doing part of it.

> Is WebRTC an open source project?
Yes. Google has provided amazing software at no cost. The spent a lot of money on GIPS, and then just gave it out that is pretty awesome. I am sure if you could quantify the amount of value WebRTC created in the world it would amaze us all. I think people want more than that though.

The OSI needs to create a new label, something like ‘viewable source’. You can’t make substantial changes or drive the project if you aren’t a Google employee. I think people find that really frustrating. For many of us this is our hobby/passion, so not being able to take part is demoralizing. This is a common pattern across many corporate projects (Android and Chromium)

I wish there was a lot more distinction between WebRTC the protocol and WebRTC the software project. I think conflating them is killing the community. If webrtc.org showed aiortc, Janus and some cool hackathon projects we could have a real community.

> Google isn’t in direct control over the future of WebRTC
I disagree. With Chromium being the dominant browser, and libwebrtc being the dominant implementation they control everything. If they release an experiment that becomes popular everyone else has to follow along, and that is just the way it is. I care deeply about WebRTC and have spent many hours making Pion WebRTC, but I am not allowed to join the IETF/W3C.

> Should you complain about Google? Maybe, but it won’t help
No. I find the WebRTC community at large very negative, and quite entitled. If people spent less time complaining and more time building solutions the world would be a better place. When I see this attitude start to leak into Pion’s ecosystem I make sure to push back quickly. I made Pion to address the complaints I heard about WebRTC, and now I hear different ones. I don’t plan on giving up until I solve all of them 🙂

At the end of the day I think the amount of people who actually care about all this can fit in one room. Most people download WebRTC, build a product and then never touch it again.

heh, I’ve never expected more than the leftovers.

At the same time the project painted itself into a corner by making promises and then not having a plan for what to do when things like developers filing bugs happen.

The state of the projects on github is… demostrating this.

As usual, I stand corrected.

– “We have official pre-compiled mobile libraries for WebRTC from Google”
These libraries are outdated currently (at least on ios). There has been no response (albeit a deleted email) to either https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/discuss-webrtc/yZPlPJQROOM/uX5zojoLAgAJ or https://bugs.chromium.org/p/webrtc/issues/detail?id=11234

For me this is understandable and somewhat expected.

The project is a complicated one with too many stakeholders and consumers inside and outside of Google. It is always a challenge to develop such things.

That said, there’s always room to improve 🙂