Chrome Is the Default Browser
The application people debug in. The engine is a different essay.
[ essay ]
Chrome is the default browser the way GitHub is the default forge: not because a standards body voted, but because the graph of users, DevTools tutorials, and “tested in Chrome” already points there. This is the product: the application Google ships, the updater, the profile, the inspect panel.1 The engine is a different essay. I am a user of browsers. I am not a Chrome engineer. Readers of darkheartlabs.technology arrive in whatever they have, and a lot of them have this.
The product work is distribution and the loop around the page: sync, passwords, the omnibox, DevTools as the IDE of HTML. Web developers debug in Chrome first. That makes Chrome’s bugs “the web” and other browsers’ bugs “compatibility.” Auto-update means the default keeps moving. Sites follow. Fedora can run Chromium or Firefox. The public web still assumes Chrome’s shapes: viewport, extensions, the way a PWA installs.
Use Chrome when you need the same inspector the rest of the industry pasted from. Test in something else on purpose. mystic-bytes is HTML. If it only works in Chrome, I wrote a Chrome app and called it a site. The default browser is a crowd. The crowd is not a spec.
— JV · Dark Heart Labs.
References
-
Chrome for Developers, “DevTools,” https://developer.chrome.com/docs/devtools. The inspect panel as the product loop around the page — Chrome the application, not the engine essay. ↩