Browsers on Linux: A Frustrating Journey

As someone who spends a fair amount of time in the terminal and values a clean, efficient workflow, I had high hopes that switching to Linux would be a smooth experience. For the most part, it has been. But one area that has caused me more frustration than I anticipated is the browser landscape. What should be a straightforward choice turned into a tour of broken rendering, sluggish performance, and missing tooling. Here is how it went.

Microsoft Edge

Given that I work heavily within the Microsoft 365 ecosystem, Edge felt like the natural starting point. Unfortunately, it quickly became apparent that the Linux port is not quite a first-class citizen. Scaling was poor, text appeared blurry, and font rendering was noticeably broken. For a browser that is supposed to be a polished, modern offering, it felt rough around the edges (no pun intended). I did not stick around long.

Google Chrome

Chrome seemed like the safe, sensible fallback. It is widely used, well supported, and I had no real complaints with it on other platforms. On Linux, however, it was a different story entirely.

To put the performance into perspective, on macOS I was seeing page load times in the region of 20 to 30 milliseconds on sites I use regularly. On Linux with Chrome, those same requests were coming back at anywhere between 300 and 700 milliseconds. That is not a minor inconvenience. That is the kind of difference that makes a browser feel broken, and in practice it made certain tasks genuinely painful to work through.

On top of the performance issues, screen artifacting cropped up regularly, making it unpleasant to use for extended periods. The final straw was Microsoft Teams, which crashed frequently enough to make it completely unreliable for day-to-day work.

Firefox

Firefox is a browser I genuinely want to like, and in terms of raw stability it delivered. It did not crash, it did not artifact, and it behaved itself. The problem came when I needed to do any serious troubleshooting. The developer tools, while perfectly adequate for general use, fell short of what I need professionally. For a DevOps engineer who regularly needs to inspect network traffic, debug web applications, and dig into request headers, the Chromium-based tooling is simply more capable. Firefox could not fill that gap.

Ungoogled Chromium

This one had promise. A privacy-respecting, de-Googled Chromium build sounded ideal on paper. The reality, though, is that getting extensions working requires toggling flags and jumping through hoops just to enable something as fundamental as the Chrome Web Store. That is not a reasonable ask for something as basic as installing extensions. When you are trying to get work done, fighting with your browser over configuration flags before you have even installed your first extension is not a trade-off worth making, and I moved on quickly.

Brave

And so, reluctantly, I landed on Brave. This one stings a little, because I was actually a Brave user before the crypto push began. Back then it was a clean, fast, privacy-focused Chromium browser and I liked it. Then the BAT token, the Brave Wallet, the crypto rewards system, and everything that came along with it started creeping in, and it made me want to find something else. I did, for a while. But here I am again.

I have hidden everything I can. The wallet tab is gone, the rewards notifications are off, and I have buried the crypto-related settings as far out of sight as possible. But I know it is all still there underneath, and that does not sit entirely comfortably with me.

The UI has also drifted away from something I enjoy using. It is hard to put a finger on exactly what it is, but the overall aesthetic has shifted in a direction I have come to dislike. It feels cluttered in places, and it does not feel like a browser built with my preferences in mind. That is a personal thing, but it adds to the general reluctance.

There is also the matter of the built-in ad blocking. Brave Shields is not something you have a great deal of granular control over compared to running your own dedicated extension and configuration. I am aware that aggressive ad blocking can cause breakage on certain sites, and having less control over how that is managed than I would like is a genuine concern, particularly in a work context where reliability matters.

But here is the thing: it works. The performance issues that plagued Chrome are gone. The crashes disappeared. The Chromium developer tools are all there, fully functional, and ready when I need them. Brave fixed the problems that every other browser on this list failed to solve.

The Linux Browser Reality

What this experience highlighted is that on Linux, you do not always get to choose your tools based on preference. Sometimes functional stability has to take precedence, and that is the compromise I have had to accept here. I do not love Brave in its current form. I find the UI uninspiring, I resent the crypto baggage, and I would rather have more control over my ad blocking setup. But it is the browser that gets out of the way and lets me work, and on Linux, that counts for a great deal more than I would like it to.

If another Chromium-based option matures to the point of being genuinely reliable on Linux, I will be the first to make the switch. Until then, this is where I have landed.