legacy.blog.ari-web.xyz/blogs/Chrome_Chromium-or-firefox_-Why-I-prefer-firefox-over-Chromium-b_9105582045.html
Ari Archer 50ea3f7f35
update @ Thu 24 Feb 19:44:01 EET 2022
Signed-off-by: Ari Archer <ari.web.xyz@gmail.com>
2022-02-24 19:44:01 +02:00

107 lines
4.3 KiB
HTML

<!DOCTYPE html>
<html lang="en">
<head>
<meta property="og:site_name" content="Ari::web -> Blog" />
<meta property="og:url" content="https://blog.ari-web.xyz/" />
<meta property="og:title" content="Ari::web -> Blog" />
<meta property="og:type" content="website" />
<meta name="theme-color" content="#262220" />
<meta name="color-scheme" content="dark" />
<meta charset="utf-8" />
<meta content="IE=edge" http-equiv="X-UA-Compatible" />
<meta content="width=device-width, initial-scale=1.0" name="viewport" />
<title>Ari::web -&gt; Blog</title>
<meta
content="website webdev linux programming ari terminal dark blog javascript opensource free"
name="keywords"
/>
<meta
content="Blog on 2021-11-09 11:56:11 EET - Chrome/Chromium or firefox? Why I prefer firefox over Chromium based browsers"
name="description"
/>
<meta content="follow" name="robots" />
<link rel="stylesheet" href="/styles/styles.css"/>
</head>
<body>
<div>
<h1>
Chrome/Chromium or firefox? Why I prefer firefox over Chromium based
browsers
</h1>
<div style="text-align: center !important;">
<p>
2021-11-09 11:56:11 EET |
<a href=".."> back </a>
|
<a href="/"> home </a>
|
<a href="/git"> git </a>
</p>
</div>
<hr />
<h2>Heads up</h2>
<p>
Just to warn you,
<strong> this post is a bit bias </strong>
, I personally prefer firefox, so my answer will obviously be firefox,
yes, firefox is not the king of privacy, but I still think it's great,
here's why.
</p>
<h2>Less bloated</h2>
<p>
Firefox is less heavy and less bloated, it's not as much of a resource,
space and in general firefox is more light and is smaller than chrome,
chromium, etc. it also takes less time to compile which matters to me a
lot because I compile everything from source, chromium takes ~60 times
as much to compile as firefox and chromium is written in C++ unlike
firefox - in rust and rust is known to be slow at compiling so if
firefox switched back to C++ - firefox would be even faster to compile.
</p>
<p>
Chromium also has a messier codebase so that also makes it prune to bugs
and generally misshaps and stuff. Firefox's LoC is 21 milion where
chromium has 35.
</p>
<p>
Firefox uses a less bloated, but less performant web engine - gecko, the
efficiency is not bad imo, but slower than blink, though as it's lighter
- i prefer it.
</p>
<h2>Easier to harden</h2>
<p>
Firefox is easier to harden making it nice for people who are willing to
spend the time tinkering around with it nicer, chromium is a bit a pain
in the ass and as far as I see the most you can harden it easily is to
install a few googled addons and that's it where with firefox you can do
a lot more. Firefox is great for tinkerers and people who like
customisation.
</p>
<h2>More customisable</h2>
<p>
Firefox allows for more customisation through
<code> user.js </code>
script (mainly for preferences) and userChrome.css which is great again,
for people who are willing to spend the time customising it. I
prefonally made firefox's interface minimalist with my userChrome and
it's nice, where with chromium I don't think I can do that AFAIK.
</p>
<h2>Chromium is targeting "tech normies"</h2>
<p>
Chromium and chrome are the most popular browsers out there, so they
expect most people using them to be "tech normies" (explained what they
are in one of my blog posts), so they add all that various abstraction
and hiding making it hard for anyone to debug it.
</p>
<h2>Firefox has better debugging tools</h2>
<p>
As firefox is not as targeted to an average windows user who just wants
to click buttons they have good debugging tools, I mainly use it for
debugging front-end, but their javascript debugging is fine too.
</p>
</div>
</body>
</html>
<!-- this is automatically generated by scripts/add_blog -->