Webkit would have to compete with other engines to retain its market share rather than abuse its monopoly power.

Their monopoly power is the only obstacle to the Web developers updating their CVs as ChromeOS developer.

Those WebGL bugs might not be present in other browser engines like Gecko or Blink.

Our app uses an embedded WebView. An alternative rendering engine would mean we could pin a specific rendering engine version in our app, and only update it for everyone after we work out any kinks with a new version. The current policies mean that we have zero control over Apple shipping new bugs in under our users' feet.

"Our product doesn't work in safari, use chrome or firefox instead"

The web is built on the foundation I can use any browser. You are going to break the fundamental promise just to avoid working around a bug?

Sometimes browsers ship bugs of the "this API just does not work anymore" variety.

When people want to get their work done, opening another browser while the original one is being fixed (which might take a couple weeks), for certain applications, is extremely reasonable for business people just trying to get their work done.

that sounds like a good short term fix. I guess I was thinking about bigger things like stadia.google.com only working on Chrome browsers. It all seems arbitrary

> The web is built on the foundation I can use any browser.

This foundation is provided by browsers and is also broken by browsers. If safari's foundation is broken then safari is the one not fulfilling that fundamental promise, not the websites now broken. So yes, don't use a browser if it doesn't work.

I think this is a pretty harsh judgement for a webGL bug.

"Best viewed in IE" was the norm for years and years, supporting only the major browsers has pretty much always been the case.

Before Opera gave up and became another Chrome reskin, there were plenty of sites that didn't work for me until I set the user agent to match another browser.

Apple have already intentionally broken that promise by refusing to implement parts of the HTML standard.

Which parts of HTML standard did they refuse to implement?

Unfortunately, Apple have a policy that the inbuilt webkit is the only browser engine that is allowed to be used on an iOS device. The iOS Chrome, Firefox, & Edge apps are just thin wrappers around the same Safari engine included in iOS.

We all know. @ben-schaaf was answering the question "how would an alternative rendering engine fix this problem".