The extensive reach of Chromium is usually a bit understated too. For example, Chromium is what powers all Electron applications., and as much as we want to gripe about the nightmare Electron has enabled, it still has wide reach. Building for Electron means building for Chromium, and building for Chromium often entails leveraging what is available in Chrome/Electron/etc over what is standard. These frequently overlap, but when they don’t, the blame is then placed on the browser rather than on the website (i.e. why doesn’t XYZ work on Firefox, when the reason is the website developer chose not to test/ensure it does work).
This gets very funny in some situations where visiting a website in Firefox throws a “not supported” page but switching the user-string to Chrome/Chromium results in the same website working just fine.
deleted by creator
The extensive reach of Chromium is usually a bit understated too. For example, Chromium is what powers all Electron applications., and as much as we want to gripe about the nightmare Electron has enabled, it still has wide reach. Building for Electron means building for Chromium, and building for Chromium often entails leveraging what is available in Chrome/Electron/etc over what is standard. These frequently overlap, but when they don’t, the blame is then placed on the browser rather than on the website (i.e. why doesn’t XYZ work on Firefox, when the reason is the website developer chose not to test/ensure it does work).
This gets very funny in some situations where visiting a website in Firefox throws a “not supported” page but switching the user-string to Chrome/Chromium results in the same website working just fine.