Overreactions?

Posted Jan 26, 2021 10:56 UTC (Tue) by ibukanov (subscriber, #3942)
In reply to: Overreactions? by smoogen
Parent article: The endless browser wars

At one point Opera contributed to Chromium a jumbo build option that reduced the build time from 8 hours to 1 and half roughly. Then a year ago Google removed those patches from Chromium tree as Google does not need them as they compile with their distributed server farm. But those patches are still maintained outside Chromium.

Overreactions?

Posted Jan 28, 2021 2:40 UTC (Thu) by fulke (guest, #140430) [Link] (1 responses)

Interesting. Could you post any references?

Overreactions?

Posted Jan 28, 2021 12:54 UTC (Thu) by ibukanov (subscriber, #3942) [Link]

On utility of jumbo builds in Chromium - https://randomascii.wordpress.com/2020/03/30/big-project-...

Google announcing removal of jumbo support - https://groups.google.com/a/chromium.org/forum/#!topic/ch... . According to my colleague who knows people on Chromium team the primary driver for the removal was a Google manager who got very upset after trying to figure out why his patch broke a build. Eventually he figured out it was due to the jumbo feature that added some small and very easy to follow restrictions on C++ code, but if one does not know about them, it can take some time to figure things out.

For getting jumbo to work with Chromium again - https://twitter.com/pati_gallardo/status/1352587508375293952

Overreactions?

Posted Feb 5, 2021 20:00 UTC (Fri) by flussence (guest, #85566) [Link]

Those patches are basically keeping KDE afloat in Gentoo right now.

It turns out making people spend 8-16 hours a day every 6 weeks compiling a half-gigabyte rendering engine that's often only used for frivolous HTML approximations of native widgets gets tiresome fast. Maybe abandoning QtWebkit was a bad idea.