|
Chrome binaries always work on older systems but Firefox binaries do not - what is the magic?
I have noticed that the prepackaged Firefox binaries do not have a good chance of working on an older system. Several times I have had to compile Firefox to work on a system. Just a few minutes ago Firefox tried to lead me down a path of replacing many system libraries. I did not fall for it this time though. I just installed Chrome instead. Took 20 seconds. 3 hours troubleshooting Firefox.
Chrome always works and never has an error.
I would suspect that Chrome was "statically compiled" but the size of the download is no larger than Firefox with both about 60MB.
So we know that Firefox has a large love for Pulseaudio and other junk which kind of lets you into the mind of the people who develop the browser.
We know that Firefox has a dwindling marketshare.
We know that the people working on Chrome are professional engineers and the ones working on Firefox are mostly doing it for "cultural change" and other nebulous reasons.
Before this becomes a total Firefox bash-fest I can think of one good reason that Chrome runs so much more easily. It MUST run reliably because last time I checked compiling from source took several days and at least 32GB RAM. I also hate that Chrome is proprietary and literally only browse Amazon Video on it. Chromium does not work wih Amazon Video.
Now that I have made clear that I don't really like either browser I would still like to know how Chrome avoids the "update your OS" pitfall?
|
