Linked by Thom Holwerda on Wed 28th Sep 2016 10:11 UTC
Internet & Networking

A number of features or background services communicate with Google servers despite the absence of an associated Google account or compiled-in Google API keys. Furthermore, the normal build process for Chromium involves running Google's own high-level commands that invoke many scripts and utilities, some of which download and use pre-built binaries provided by Google. Even the final build output includes some pre-built binaries. Fortunately, the source code is available for everything.

ungoogled-chromium tries to fix these things.

Permalink for comment 635022
To read all comments associated with this story, please click here.
Member since:

In the past, Firefox developers have been difficult to work with in my experience. The same problem exists with most open source projects though, if you're not the big 3 you get ignored. If you're using Linux, windows or mac os, people will take your patches. If you're trying to get anything else to work, they have excuses like bloat, irrelevance, etc. Well of course the other OS is irrelevant if it doesn't have firefox right? That's what you're trying to fix.

I've gone through re-porting firefox a few times and the security manager code is a nightmare every single time. Then there's the crap code added for HTML5 video/audio, etc around firefox 4. It hasn't gotten any better. In fact, things have gotten worse because now it fails to build with some of this stuff disabled. At that point, you're battling the third party libraries compatibility with your OS on top of firefox.

Anyone who thinks firefox is awesome hasn't tried to get it to work in another OS before without the UNAME already being supported.

I will say that they've made huge leaps on memory usage and performance in recent releases on supported platforms. I've actually considered switching back to it in OS X because it does feel faster than chrome and safari now. The UI stuttering from chrome isn't there.

With all this said, other browsers have their own issues. Chromium has a terrible build system. It's fragile, non standard and buggy. When I actually prefer automake/autoconf you know things are bad.

Another issue with chromium is that if you actually enable all the google services, you have to give it a developer token. If you're building packages for an OS for redistribution, those hits go against your account and the limits are pretty low. It seems counter intuitive that google wouldn't want people to access their own services.

Reply Parent Score: 2