W3C home > Mailing lists > Public > public-webrtc@w3.org > January 2018

Re: What would you like to see in WebRTC next? A low-level API?

From: Justin Uberti <juberti@google.com>
Date: Tue, 23 Jan 2018 23:01:28 -0800
Message-ID: <CAOJ7v-0HaVVvfJFeLSb8RoXcWE3imbz+Cr3WZ=bXhq542zfM7w@mail.gmail.com>
To: Bernard Aboba <Bernard.Aboba@microsoft.com>
Cc: Peter Thatcher <pthatcher@google.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On Tue, Jan 23, 2018 at 3:37 PM, Bernard Aboba <Bernard.Aboba@microsoft.com>

> I'll provide some more detailed comments later, but would like to provide
> a few high-level thoughts (with my Chair hat off).
> Overall, my experience with developers is that they care most about
> stability and functionality.
> If there is a way to make something work, and if it is stable enough to
> deploy in production, they will incorporate it into their applications,
> even if many of would consider it a "hideous hack".
> So enabling something new, useful and solid is a good way to gain
> developer mindset.
> Doing the same thing in a more elegant way can be intellectually
> satisfying, but can be hard to convince developers to utilize if their
> existing code can do the same thing, albeit somewhat more clumsily.
> All this to say that if the goal is to create things that developers will
> use, it is often best to start from problems:  things developers want to
> do, but have not been able to do so far.

This is a reasonable take. On this topic, one thing that I continually hear
from developers: they want more control over their destiny, e.g. to get
consistent performance across browsers, and even across versions of
individual browsers.

Peter's proposal takes allows the developer to own much more of the code
that is actually running in a WebRTC call. This not only allows for more
innovation, but also provides a much deeper level of control.
Received on Wednesday, 24 January 2018 07:02:11 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 24 January 2018 07:02:12 UTC