UNGOOGLED CHROMIUM MAC CODE
UNGOOGLED CHROMIUM MAC MAC

Many people including the core devs are against it. It seems counter intuitive that google wouldn’t want people to access their own services.Ungoogled-chromium doesn't have automatic updates because that would require a background service to function. If you’re building packages for an OS for redistribution, those hits go against your account and the limits are pretty low. When I actually prefer automake/autoconf you know things are bad.Īnother issue with chromium is that if you actually enable all the google services, you have to give it a developer token. With all this said, other browsers have their own issues. The UI stuttering from chrome isn’t there. I’ve actually considered switching back to it in OS X because it does feel faster than chrome and safari now. I will say that they’ve made huge leaps on memory usage and performance in recent releases on supported platforms. At that point, you’re battling the third party libraries compatibility with your OS on top of firefox.Īnyone who thinks firefox is awesome hasn’t tried to get it to work in another OS before without the UNAME already being supported.

In fact, things have gotten worse because now it fails to build with some of this stuff disabled.

UNGOOGLED CHROMIUM MAC CODE

Then there’s the crap code added for HTML5 video/audio, etc around firefox 4. I’ve gone through re-porting firefox a few times and the security manager code is a nightmare every single time. Well of course the other OS is irrelevant if it doesn’t have firefox right? That’s what you’re trying to fix. If you’re trying to get anything else to work, they have excuses like bloat, irrelevance, etc.

UNGOOGLED CHROMIUM MAC MAC

If you’re using Linux, windows or mac os, people will take your patches. The same problem exists with most open source projects though, if you’re not the big 3 you get ignored. In the past, Firefox developers have been difficult to work with in my experience. I also like DuckDuckGo, and on the rare occasion it doesn’t find something, it always has !g shortcut for google. It just seems to behave more like an X11 program than Chrome/Chromium/Opera. Could even bee that I think Epiphany uses the GTK3 implementation of webkit.Įither way, I prefer Firefox as well. Not sure if this is a difference in which particular revision of webkit it’s using or if it is some specific additions depending on browser. While Opera now pretty much renders / acts the same way as Chrome/Chromium, it does not act the same as Epiphany, which also uses Webkit. Webkit itself seems like it’s not exactly the same across the board. It wasn’t the best engine out there, but they chose KHTML, and the rest is history.Īnd as your point proves, Opera no longer uses their own engine, and instead uses webkit as well.įunny thing is, last time I used Konqueror (probably 1-2 years ago) they had the option for both KHTML and Webkit, and they rendered the same page slightly differently.

They could also very easily have found the cash to buy Operasoft and use their engine. They could just as easily have forked the Mozilla engine.

When Apple created WebKit, the did so by forking KHTML, which was a rendering engine created for the KDE platform, and virtually unknown outside of KDE users. Why bother forking forking the lesser option?īecause at some point that attitude leads to the lesser option disappearing entirely.Īnd the ‘lesser option’ may actually hold some benefits.

Ungoogled chromium mac