Why does it take so long for Chromium updates to appear? Chrome has had two (2) updates last month - with supposedly important security related fixes, but Chromium is still on the version before last. Anyone know why this happens?
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Chromium delays
- Thread starter davidlv
- Start date
- Sort by reaction score
My guess is that the Chromium release engineering "team" (it might just be one person) is a volunteer who gets paid to do other things.
In my case, I use the Marmaduke ungoogled-nosync Chromium build from Woolyss (both Windows 10 64-bit and macOS 64-bit). Sometimes his builds show up a day or two later, sometimes a week goes by. At least once there was no build for two weeks after the Chrome release; I assume he was on vacation. Sometimes the macOS build shows up first, other times it's the Windows build.
A more stark example: the GIMP image editor. The GIMP engineering team continues to release new versions and the Windows release team seems to have an installer ready to download upon release. However the Mac distribution is stuck on version 2.10.14 which is nearly a year old. It appears that the GIMP project lost their Mac release engineer.
The code is there so if you're a Mac programmer you can build it yourself (I'm not adept at such endeavors). But there is no one who has stepped up to the plate to make a publicly distributable macOS package of the current GIMP.
Feel free to ask the Chromium development team directly. I'm guessing you will get a response like "we are always looking for volunteers to help with our development efforts."
In my case, I use the Marmaduke ungoogled-nosync Chromium build from Woolyss (both Windows 10 64-bit and macOS 64-bit). Sometimes his builds show up a day or two later, sometimes a week goes by. At least once there was no build for two weeks after the Chrome release; I assume he was on vacation. Sometimes the macOS build shows up first, other times it's the Windows build.
A more stark example: the GIMP image editor. The GIMP engineering team continues to release new versions and the Windows release team seems to have an installer ready to download upon release. However the Mac distribution is stuck on version 2.10.14 which is nearly a year old. It appears that the GIMP project lost their Mac release engineer.
The code is there so if you're a Mac programmer you can build it yourself (I'm not adept at such endeavors). But there is no one who has stepped up to the plate to make a publicly distributable macOS package of the current GIMP.
Feel free to ask the Chromium development team directly. I'm guessing you will get a response like "we are always looking for volunteers to help with our development efforts."
Thanks, that makes sense! Here is a link to that Chromium builds from Woolyss:
Download latest stable Chromium binaries (64-bit and 32-bit)
Download latest stable Chromium binaries for Windows, Mac, Linux, BSD and Android (64-bit and 32-bit)
chromium.woolyss.com
Last edited: