先说结论

Skip Can I Use. Query 260k rows of SQLite first.

If you already use GPT or Claude and still spend your day bouncing between a browser tab, a chat window, and your editor, this is the compatibility version of the same mistake: refreshing Can I Use for each question. Do that long enough and a simple check turns into manual lookup, manual copy-paste, and one more round of rework.

Browser compatibility is not a web table; it is data that should answer SQL questions. AI tools are not just coming for code work. They are coming for the tiny context switches between tabs.

为什么这次值得看

A compatibility page is fine for a one-off answer. The problem starts when every decision begins there. The visible cost is time. The hidden cost is that you never get to ask the higher-value question for a codebase: which prefixes, experimental features, or browser combinations are most likely to bite us?

That is why simonw/browser-compat-db is more than a neat packaging trick. In the 2026-06-24 README snapshot, the database already contains 19,834 features and 260,715 support rows, split into normalized tables such as features, support, feature_tags, and browser_releases, with Datasette Lite bundled so you can query it directly.[S001] At that size, a compatibility page starts to look like the slow path.

关键证据

MDN points the same way. It describes Browser Compat Data as machine-readable, and lists Can I Use, VS Code, WebStorm, Firefox, and TypeScript as tools that already consume it.[S002] That matters because the job is no longer just answering a yes/no question about one API. The better question is what you should query before this becomes a compatibility bug.

Many people think they need a stronger model. Often they just need fewer windows.

Boundary line: this is based on the simonw/browser-compat-db README snapshot dated 2026-06-24 and current MDN Browser Compat Data docs, not a production rollout benchmark. It is also not an argument that every team should build its own compatibility stack; sometimes a quick page lookup is enough. But if someone on your team is still refreshing Can I Use for every decision, share this with them.

适合谁 / 下一步怎么用

最后落到动作：share