What does HackerNews think of browser-compat-data?

Just noting that the browser support matrix is right here: https://web.dev/patterns/advanced-apps/contacts/#:~:text=con...

It's an Eleventy widget powered by MDN's browser-compat-data: https://github.com/mdn/browser-compat-data.

See also browser-compat-data, the source data for Can I Use? and the Browser Compatibility tables at the bottom of MDN reference pages. I believe VS Code and other tools also rely on it.

https://github.com/mdn/browser-compat-data

I should really write a script to generate this from MDN's browser compatibility data (https://github.com/mdn/browser-compat-data), but many APIs aimed at making browsers more competitive with native apps tend to lag behind or not get implemented at all in Webkit.

We only got working IndexedDB as of Safari 10 and Service Workers in Safari 11, both multiple years after support landed in stable Firefox. There's no support for WebXR, Web Push, or WebAuthn. Safari still can't display WebP images, show WebM (VP8/9) movies, or play Opus-formatted sound. Safari doesn't understand the current version of referrer-policy headers. Safari doesn't implement the String.prototype.matchAll() method. There's no support for getDisplayMedia(). Depending on how you count, we've been waiting seven years for getUserMedia() in Safari, and it's still not fully functional. Safari can't animate changes to CSS grid template rows/columns, or use overflow-inline / overflow-block media queries.

...it's a big weird grab bag of features, but a broad surface area nevertheless. And you have to wonder if some fringe APIs wouldn't be more popular if we could actually compete on bringing the full Web platform to iOS devices in a timely manner.

We're working on this... https://github.com/mdn/browser-compat-data, https://github.com/mdn/data ...but it's going to be a slow process.