HN user
Much of this could have been avoided by knocking some sense into the entities that constantly propose new features and those who implement them as native browser elements instead of JS libraries where possible.
That's what Google did with the shadow DOM they used on YouTube: since Firefox had no support for it they wrote a polyfill (which is a JS library to emulate a feature) and the resulting performance was terrible.
To the extent Chromium has a monopoly, Chromium bugs are the standard and sites will depend on them. Yes, this is already true to some extent, but it could get much worse. So fixing bugs would get harder.
If instead of Blink we had Blink AND Gecko, instead of Chromium bugs being the standard, Chromium AND Firefox bugs would be the standard. How is having to implement workarounds for TWO engines worse than having to implement workarounds for ONE engine?
Well, it's Russia... the land of the oligarchs.
How does this work if you don't give bluetooth access to the apps which include those toolkits?
My iPhone has a BSD-licenced kernel. Having that kernel under that licence benefits me as an end user of the product. Maybe having used another kernel would've resulted in a less stable mobile that would not have taken off.