In practice, I kind of doubt that standard libraries would actually include
multiple implementations of the web platform.

It also seems like it could break update cadence, since standard libraries
don't have nearly as rapid or streamlined and mechanism for pushing out
updates. It seems like they could ossify whatever arbitrary version got
shipped out in a major stdlib release.

I echo the sentiment that this doesn't feel like the right approach to the
problem, and that focusing on a package ecosystem makes more sense.

On Wed, Jul 18, 2018, 17:13 Botond Ballo <> wrote:

> On Wed, Jul 18, 2018 at 8:04 PM, L. David Baron <> wrote:
> > It feels like this bakes into the C++ language the idea that a
> > machine only ever needs a single implementation of the web platform.
> >
> > I (and I think many others at Mozilla) think that users are better
> > served by competition among implementations of the Web's technology,
> > since it allows competition to better serve the interests of users
> > and allows more flexibility in the evolution of the platform due to
> > fewer mistakes getting quickly baked in to the platform by
> > compatibility.
> >
> > This makes me think it's a bad idea to standardize a Web View API as
> > part of C++.
> Is having a Web View API fundamentally incompatible with there being
> multiple implementations to select from?
> Suppose the API had a mechanism to query a list of available
> implementations, and you could specify which one to use when
> instantiating a web view - would that address this concern?
> Cheers,
> Botond
> _______________________________________________
> dev-platform mailing list
dev-platform mailing list

Reply via email to