I've been using Firefox version 47 for the past couple of days. And it's been working well. This isn't for my day job, where I beat the hell out of the browser, but for "research" (aka looking things up) while learning programming.
Nothing cost $ .
I should probably give it a try for my real work and see how it holds up.
Update: Firefox did better than I thought but not good enough.
Slow rendering in Google Maps was annoying.
I want Firefox to be competitive. I'd rather have fewer eggs in Google's basket. But my web production workflow is just too many windows of pain.
The Unix/Linux desktop environment GNOME's many components include a full web browser that used to be called Epiphany and now goes by the very non-Googlable name Web. Yes. it's a Web browser called Web.
Back in the GNOME 2 days, I used it a lot. That wasn't just the GNOME 2 days but the Gecko days, when Epiphany was based on Mozilla's Gecko engine rather than Apple/Google's WebKit.
In the early WebKit days, I think Epiphany/Web went downhill a bit.
Now I use Google Chrome much of the time, though I know in my heart that I shouldn't. I'm usually logged into Google Services for my job, and Google is getting into everything I do.
These days Firefox is just frustrating. Once I get 10 tabs open, it tends to hang when Chrome doesn't.
Maybe a basic browser like Epiphany/Web can help me. Maybe not.
I'll give it a try and let you know how it goes.
Update: Epiphany/Web works very well. I can't say for sure that it's "lighter" than Google Chrome, especially since it uses the same Webkit engine.
What I can say is that for general-purpose web-browsing, it is very fast and stable. And I bet Google is tracking me a whole lot less.
Epiphany is a simple browser. Like Firefox was in its early days.
It's well-integrated as a GTK3 application, so it'll look good either in GNOME 3, or (in my case) among all the other GTK3 apps I'm using in the Xfce desktop environment.
For search, Epiphany defaults to Duck Duck Go which bills itself as "the search engine that doesn't track you," and so far I'm happy with it. It's nice to have an alternative to Google, even in a Web browser using the same engine as a browser that is most definitely tracking you.
I'm not saying I will give up on Google Chrome, especially for my , but when it comes to personal browsing, I can see myself in Epiphany much of that time.
Hey Linux users, are you using GNOME Tweak Tool to choose the "Dark" theme, making your GTK3 applications dark and causing problems with white-on-white text in the Firefox browser?
I have. Even though I almost never use GNOME 3, I do have it installed, and the GNOME Tweak Tool's "dark theme" switch enables me to turn GTK3 applications like Firefox "dark" in their styling. Except that often you can't read text boxes on web sites because the "dark" theme turns the text white while also leaving the background white.
If you're having the same problem I am with Google Chrome crashing while running the proprietary AMD Catalyst video driver in Fedora 20 (or any other version of Linux), I have a fix.
My thought was that I could play with command-line switches to "trick" Google Chrome into running.
(Note before we begin: I think different distributions have different commands to run Google Chrome or Chromium in the first place. In Fedora, calling
google-chrome runs the browser.)
I found a huge list of command-line switches for Chrome and Chromium from Peter Beverloo's web site and started looking it over and trying a few.
This one worked:
$ google-chrome --disable-gpu
Peter's page describes
--disable-gpu this way (and links to this portion of the content-switches code for Chromium):
Disables GPU hardware acceleration. If software renderer is not in place, then the GPU process won't launch.
This means that I'm back in the Google Chrome-running business. I'll have to add this modified command-with-switch to my Xfce panel so I can run Chrome without the terminal.
And now you can, too.
Am I really the only person having trouble with the Google Chrome web browser while running the propretary AMD Catalyst video driver in Linux?
I pulled the AMD Catalyst driver from my Fedora 20 system to do some tests. Among the things that started working: The Google Chrome web browser, which in recent weeks kills X while running under the proprietary driver.
It turns out that Google Chrome runs fine with the open Radeon driver.
As always, AMD Catalyst giveth (cooler operation, working suspend/resume) and taketh away (Google Chrome fails, trouble updating when driver doesn't support new kernels, general wonkiness).
A couple days ago, there was a Google Chrome update, and for some reason the browser began working once again on my Fedora 20 system.
Now it's broken again.
It could have been a Mesa update in Fedora. Or something completely different. It could be the dubious AMD Catalyst/fglrx installation I have going, using Fedora 19 packages in Fedora 20.
Whatever it is, Google Chrome is broken again.
I even tried Spot's Chromium repo for Fedora. Chromium crashes X just the same.
Is it just me, or is anybody else having a problem with Chromium/Google Chrome in Fedora?
Google Chrome (using the Google repository because Fedora doesn't package Chromium) is working once again on my Fedora 20 system.
It had been broken for a few weeks. Whenever I started the browser, it would segfault and kill X.
Google pushed a new stable version of the browser today to its Fedora repository. I did the update, started Chrome and am now running it with no crashes and no problems.
I don't run Google Chrome all that often in Linux, though I run it all the time in Windows.
But I do keep Chrome, via Google's repository, on my Fedora 20 system.
So I try to run it today and it segfaults (I know because it kills X and I see "segfault" in the console messages).
I searched (yes, using Google) and couldn't find anything on this.
I can't remember if I've used this particular version of Google Chrome successfully before my most recent reinstall of AMD Catalyst (via the Fedora 19 packages in RPM Fusion).
Right now I'm unwilling to uninstall Catalyst just to test Chrome, especially because I'm primarily a Firefox user on this machine.
I spent quite a bit of time running Google Chrome/Chromium on both Windows and Linux, but between feeling uncomfortable giving away so much data to Google (when logged in on Chrome) and how well Firefox performs on Linux (which is very well from what I can see), I now use Firefox about 99 percent of the time in Fedora 20.
But on my Windows 7 work machine, which is a more powerful (quad-core AMD to my laptop's dual-core, with 8 GB of RAM to the laptop's 4 GB), I flip it, using Chrome about 99 percent of the time.
So I've been switching it up to see how I might like using more Chrome in Linux and more Firefox in Windows.
I'll keep it short. There's nothing about Chrome on my laptop in Fedora 20 that makes me want to use it. It's no faster and no more stable. And SELinux doesn't much like it (and I get warnings).
I spent the whole day yesterday in Windows 7 on my big box running Firefox (version 27 on both machines for the record) for everything. It was measurably slower, and I had a few periods of non-responsiveness, especially with my customary 15-20 open tabs.
This means I'll be sticking with Firefox on my Linux-running laptop (and for my personal use, where I'm not so crazy about Google spying and Chrome on my workplace desktop, where I'm already using Google Apps and am not doing any personal business (and could care less if Google knows about my web use as it relates).