Comparing Chromium Development at Google and Igalia

Commenters debated Gentoo maintainers' decision to stop building Chromium from source after upstream allegedly failed to test builds with supposedly "optional" features disabled. rmunn cited the LWN report and noted maintainers' frustration with dozens of USE flags and 15-16 hour compile times, which make exhaustive testing impractical. Some commenters framed different motivations: shevy-java condemned developers who enable Google's Chromium as supporting an "AdChromium empire" and wondered about financial tradeoffs, while throwaway2037 speculated about personal economics. Others pointed to alternative approaches: msdz asked how Helium handles an opinionated Chromium base, and Mic92 suggested reducing the number of flags.

Opinion split over where responsibility lies and what the pragmatic fixes are. Several commenters (rmunn, others) argued upstream created the myriad of optional features and Gentoo only mirrored them, so upstream should acknowledge when features are effectively mandatory; octoberfranklin countered that Chromium's CI could cheaply exercise flags (compile-but-not-link or run gn permutations) and thus avoid breaking distributions. shevy-java and others said Gentoo itself chose a policy of exhaustive configurability and therefore bears some burden, while rmunn outlined the real choices: test all combinations, expose flags without testing, stop exposing flags, or stop packaging - the latter being what happened.