A ha, here’s the thing: webstatus.dev?q=baseline_s...
Thanks @alangdm.bsky.social!
11 replies
We should all be super sceptical of the "widely available" thing. Users shouldn't be on 30 month old browsers, ever. The Cheome team should know better than to create an attractive nuisance like this.
My hunch was that 30 months was too short to match reality 🫣😅
It's not. We keep doing audits for Office to see enterprise use, and it's generally a security problem for any enterprise of they have users on engines that old. We're doing them a favour by being more aggressive in most cases.
*if
*sigh*
yeah, but nowadays the long pole are private iPads that don’t get iOS/Safari updates anymore.
and Chrome on older macOS as well.
On older Macs you can do almost nothing, because the AppStore is broken and the web is broken as well. Too aggressive everything.
The idea that we'd create a disincentive to use a feature for almost *3 years* after 90+% uptake is 🤦🤦🤦
I get the ESR thing, but this isn't a responsible way for us to be advising web developers about their options. The name alone is a real problem.
Ah, yeah. I get that. I would welcome a Baseline that was PE-aware and usage driven too
There are a few use-cases. E.g., when collecting RUM data we want the script to work mostly everywhere, not crash on unsupported syntax, so we know the # of users left on older browsers. We've been (carefully, to avoid bloat) transpiling to ES5 for this, but "widely available" might be a good fit.
Features aren't all equal as well, like fetch priority could be used as soon as chrome supported it, and without waiting for widely available etc.