Check Baseline before you check caniuse
Baseline turns "which browsers support this" into a yes or a no, and it is now built into MDN, the docs, and a linter you can run in CI.
Support tables are a research task. Baseline is an answer.
A feature is Newly available once it works in the current version of every major engine, and Widely available thirty months later, which is the point at which the long tail of un-updated devices has mostly caught up.
Why it matters: “can I use this” stops being a judgement call you re-make on every project. Widely available is a yes. Newly available is a yes with a fallback. Neither is a no with a progressive enhancement.
The part people have missed: it is not just a website. MDN pages carry the status inline, and eslint-plugin-compat and the browserslist query baseline widely available let you fail a build on a feature your support policy has not reached yet.
That turns browser support from an argument in code review into a config line, which is where it belongs.