This is very early exploratory and will likely go nowhere.
My dissertation looked at Receiver Operating Characteristic... (mining my memory...) To get 100% True Positives identified, you have to accept 100% of false positives will be in the set. It got me thinking....
- Is there an analogy to ROC to get 100% compatibility on a site you have to accept 50% of APIs not useable because it's not in other browsers. Or to have 100% of people using your site, you will only have X% of web platform available to use..
- Can it describe the state of the ecosystem?
- (sorry for this framing) Gecko adds a feature before anyone else there's less incentive for developers to use it because the user-base is smaller. How would we help change this incentive?
- Chromium adds a feature before anyone else, there's a lot of usage of Chromium browsers - but ecosystem rightly wants to use things that are broadly compatible.
- WebKit adds a feature before anyone else US and EMEA tends to move because huge amounts of their revenue is generated via iOS + Safari.
- Actually do we know what developers say they support? Yes, Quarterly survey says: Chromium/Blink, WebKit, Gecko.
- Can it be used to help prioritze compat across all browsers? (More research needed)
- Can we look use caniuse compat data? WPT?
Can we use this to determine how safe it is to change an API, or remove it (not purely just usage counter)
About Me: Paul Kinlan
I lead the Chrome Developer Relations team at Google.
We want people to have the best experience possible on the web without having to install a native app or produce content in a walled garden.
Our team tries to make it easier for developers to build on the web by supporting every Chrome release, creating great content to support developers on web.dev, contributing to MDN, helping to improve browser compatibility, and some of the best developer tools like Lighthouse, Workbox, Squoosh to name just a few.