There are two very distinct parts here and the article does a good job of muddying it.<p>Chromium: the base of Chrome, which is opensource - is developed in part by google and many other companies, including Microsoft, Apple, Brave, and dozens of others who depend on the chromium ecosystem. Google is not "financing" these companies, they are contributing to and benefiting from opensource bidirectionally and the ecosystem benefits from compatibility streamlining. 94% of commits to chromium from Google is also cherrypicked, many are automated commits to update libraries and pull in code from other repos and projects, and they do have a google/chromium handle on them as reviewers and signoff. It is true that they are the primary stewards and that most code in chromium passes through google hands before arriving there - but a good amount is chromeOS/android commits. Most downstream projects prune a ton of this "clank" out - claiming that commits in those directories are supporting 3rd party browsers is bunk. Google’s own docs say any code “that isn’t written by Chromium developers” must live in //third_party, this is enormous: v8, Skia, ANGLE, FFMPEG, ICU, OpenSSL - codecs, llvm... keeps on going. When a new upstream tag is imported, the roll commit is stamped with a Google email, throwing off this number considerably. The committer field shows the Google engineer or CQ bot, not necessarily the external engineer who produced the diff.<p>Google Search contracts: it is true that Mozilla and Apple receive large royalties in order to have Google be the default search engine in those browsers - in addition to android vendors and other platform partners. I don't think this amounts to 80% of "funding" on those browsers.<p>The second part is far more dangerous than the first - some care needs to be made rolling these claims together.<p>Everyone else could jump on quantum/gecko if they really felt like it was critical to their business to not use google-centric codebases.