Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I wish this was the case, I doubt it'll be the case. Suppose for example that the foundation agrees that Manifest V3 is a bad idea (and, objectively, it is an awful idea). I can't imagine a world where the contributors from Google (which currently still make up the vast majority of the commits to the Chromium codebase) go back on their steps and re-implement support for V2, which would basically go against the profitability strategy of their own employer.

Same for intentionally crippling Google websites on non-Chromium browsers: given how deliberate such acts of crippling are, I have reasons to believe that it's part of Google's "works with Chrome" strategy, and I'd doubt that Google employees can do much against it.

The only way to fix the governance of Chromium is to effectively chop all the threads that connect it to Google. As long as Chromium developers who are employed at Google won't do anything that goes against the strategy of their employer, you can't have fair governance.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: