An important piece in everyday life is the browser, considering the new trend of storing data and accessing applications in the cloud.
Among the browsers landscape, the choice is actually finite because developing and maintaining one is expensive. But, which browser should you choose? One that offers speed or one that is secure? Does it respect your privacy?
In the current post, we will showcase browsers with a user-friendly GUI which both novices and experts can use. Firefox and Google Chrome will be highlighted as well as their forks and brand new browsers; attenction is paid to the consumer privacy.
Prerequisistes: None. Both beginners and advanced users can enjoy this post; it tries to explain every technology that is needed to discuss the various browsers and their differences.
Browser Market Share Worldwide 2017
Google Chrome 1
Google Chrome has been the most used browsers in the last year with a wide gap from the other alternatives. Why? Because rendering a page is really fast and it is integrated with Google services.
But it’s a Google application, you can’t expect that it will respect your privacy; settings don’t help either. And it isn’t an open soure browser.
The rendering engine (the part that reads the HTML page and prints the formatted output) of Google Chrome is called Chromium and is also distributed as a separate browser. It’s basically Google Chrome minus some extensions and plugins. Privacy is a little better but it’s still Googlish.
Here we are at the first privacy-aware browser: Iridium, a fork of Chromium, private and secure by default. The project has been released recently, but it seems already abandoned: the latest commit to its codebase is dated in November 2018. No fixes or security update since then.
ungoogled-chromium, is a fork of chromium with privacy improvements where Google traces have been removed. It is a drop-in replacement so you can download the browser and start using the same interface you’re used to.
Mozilla Firefox 6
Another pillar of privacy-aware browsers is Mozilla Firefox. It is fast (especially with the new Quantum engine7) and easy to use. The only problem is that Mozilla often makes opinionated choices 89. But Firefox is open source and it would be a huge loss to waste its code; this is why we will overview some of its forks.
It’s important to state that Firefox isn’t privacy-aware by default, but the opt-out and relevant settings are just few clicks away, and all the sneaky extensions enabled by default (like Mr. Robot extensions9) can be disabled.
If you still want to use Firefox, follow PrivacyToolsIO guide10.
XUL (XML User Interface Language) is Mozilla’s XML-based language for building user interfaces of applications like Firefox.
It is a subset of XML made for creating add ons that change Firefox user interface; Mozilla deprecated XUL-based add ons at the end of the 201716. Basilisk developers still believe in a future of this technology and want to improve it.
The rendering engine it’s called Goanna17 and it’s a fork from an old version of Firefox (v25) that have diverged significantly over the years.
The project seems interesting, but after a bit of digging, I’ve found this issue18 in the OpenBSD work in progress ports tree. Basilisk developers (they also develop Pale Moon19) opened it to make the port comply with the licence, and the terms used are not polite at all. Package and ports maintainers are often volunteers so there is no point in making such an approach for whatever reason. Because of this, Basilisk developers don’t seem to deserve the users’ trust, I suggest to use some more trustworthy project instead.
Note: A OpenBSD port is a set of files (Makefiles) that describes where to fetch the source of a software and how to compile/install it. The pre-compiled binaries offered by OpenBSD are built using the ports.
GNU Icecat 20
Icecat browser targets people who care about their privacy but code freedom too. It is based on Firefox ESR (Extended Support Release) and consists in a set of patches that remove all non-free code and enhance privacy.
Some security extensions like LibreJS21 and Searxes’ Third-party Request Blocker22 are shipped with Icecat but they can be disabled with a click in the homepage, restoring the usual surfing experience (these two extensions break many sites).
In a fancy GNU style, Icecat allows a limited set of extensions, the free ones; indeed Stallman wouldn’t approve non-free extensions!
Download version 60.3.0!23 (File: icecat-60.3.0.en-US.gnulinux-x86_64.tar.bz2)
As strange as it sounds, Librefox is not a fork. It instead consists in a bunch of configuration files applied to vanilla Firefox. Privacy extensions and sane settings are shipped with it, unneeded features are removed (like crash reporter and updater). An optional Dark theme25 crafted by Librefox team is available.
The first version of Librefox has been relased in November 2018, so it’s a pretty new and interesting project. As of January 2019, Librefox distributes the configurations files that need to be applied manually to vanilla Firefox, by unpacking them in the installation directory. Developers stated that a complete build is planned26.
Pale Moon 28
Pale Moon is a fork of Firefox dated back in the 2009. It supports XUL and offers the old Firefox UI. The rendering engine is the same of Basilisk so they are almost the same in terms of speed.
For reason stated above about its developers, I suggest using other more trustworthy alternatives.
Waterfox’s philosophy is close to Librefox, but dates back in the 2011; it has a dedicated website with all the relative informations and the full build download.
It allows the installation of every plugin (unlike Icecat) but its version lags behind: at the time of writing the last release is 56.2.6, while Firefox latest stable release is 64.0.2.
Dooble is a Qt browser written with privacy in mind that uses QtWebEngine (Chromium integration in Qt libraries).
Falkon, which changed name in the latest release, is the former Qupzilla, a Qt based browser made by KDE; it uses QtWebEngine.
GNOME Web 34
GNOME Web, formerly known as Ephiphany, is the browser of choice for GNOME desktop and Elementary OS. It features a clean interface (which pair perfectly with the above desktops) and uses Webkit35 (Apple open-source browser engine). The latter is also its biggest flaw: Webkit is slower than its competitors (both Firefox browser engine and Chromium).
Another worth mentioning feature is the desktop integration with GNOME:
Install it from your distro repository!
Another Qt browser that’s developed by the KDE team. Its peculiarity is its support for both QtWebEngine engine and KHtml37 engine. Right-click and then choose “Render with KHtml” or “Render with WebEngine”, this is all it takes to switch between the rendering engines.
The KHtml browser engine was choosed by Apple as starting point for its WebKit, but it’s currently unusable because of inability to render Html5 properly.
Install it from your distro repository!
Midori is a lightweight browser, originally developed for the XFCE desktop (indeed its UI reminds this desktop); it uses WebKit.
Google literally eating RAM
In term of system resources, browsers have made huge improvments in the last years, especially Firefox. If we ordered browsers in terms of RAM usage (from highest to lowest), it would be: Google Chrome, Firefox and then all the others.
QtWebEngine, even though it is based on Chromium, doens’t consume the same amount of RAM; considering that browsers using this engine also have a lightweight GUI, they are perfect for low-end machines. Along with WebKit browers as well.
Notes about add ons
Firefox has recently deprecated support for its extensions API to support the Chrome extensions API; as a result, Chrome and Firefox (including their forks) share the extension format. This is not true for all the other browsers listed in this post: each one supports its own format and has its own add ons (usually not more than 10).