Comparing Chromium Development at Google and Igalia
signa11
29 points
2 comments
October 16, 2026
Related Discussions
Found 5 related stories in 114.0ms across 9,619 title embeddings via pgvector HNSW
- Google ending ChromeOS support two years early rbanffy · 195 pts · September 29, 2026 · 48% similar
- Kagi Ends Orion Browser Development for Linux, Will Open-Source It MilnerRoute · 11 pts · October 05, 2026 · 48% similar
- Show HN: Watching browser fingerprinting calls via Chromium's Blink layer brnbs · 11 pts · August 10, 2026 · 48% similar
- Google Chrome Arrives on ARM64 Linux, Widevine DRM Included twapi · 85 pts · July 27, 2026 · 47% similar
- Chrome's Breaking and Entering ingve · 25 pts · July 24, 2026 · 46% similar
Discussion Highlights (1 comments)
rmunn
Also worth noting https://lwn.net/Articles/1097760/ - Gentoo has given up on building Chromium from source, because upstream "do not test their builds with any of their allegedly 'optional' features disabled" and "[i]n the case of Chromium, keeping all the toggle switches working (despite chronic neglect from upstream) is a monumental, nigh-insurmountable task." One maintainer said he could not possibly test all the combinations of USE flags in the Gentoo build, since his laptop took 15-16 hours to compile Chromium (I presume for just one build, which would have to be repeated 2^N times to test all possible flag combinations). Much more in the LWN article, I'm not going to quote everything.