Stop Using Chrome.

I deleted Chrome from my main machine two weeks ago. All of it.

After years of telling myself I was "too busy" to switch browsers, the news of an actively exploited sandbox RCE in all Chromium versions finally broke my complacency.

I needed to see what life was like on the other side – not just for security, but to understand my own digital dependencies.

What I found was a startling mix of relief, frustration, and a deep sense of betrayal by the browser I'd trusted for over a decade.

This wasn't some hypothetical threat.

We’re talking about a flaw that allows malicious actors to execute code remotely on your computer, bypassing the very sandbox designed to keep browser processes contained.

It's the digital equivalent of someone picking your front door lock, then also bypassing the alarm system you thought was protecting your valuables. And it's happening right now.

The Setup: My Chrome Addiction, Disrupted

For over ten years, Chrome was my digital home. Every tab, every extension, every saved password and autofill entry was meticulously synced across my devices.

It was convenient, fast, and, I thought, secure enough.

I’m a generalist who covers tech culture and trends, so I spend literally all day online, switching between research, writing, and social media. Chrome was the backbone of that workflow.

Then the reports started hitting Hacker News: a critical RCE vulnerability, actively exploited in the wild, affecting all Chromium-based browsers.

Not just Chrome, but Edge, Brave, Opera, Vivaldi – if it runs on Chromium, it was on the hit list. This wasn't just a bug; it was a zero-day under active attack.

My immediate thought was, "But I'm careful!

I don't click suspicious links!" But an RCE means the vulnerability can be triggered just by visiting a compromised website, or even one serving malicious ads.

Suddenly, my careful browsing habits felt irrelevant.

I knew I couldn't just talk about the vulnerability; I had to experience the mitigation. So, on September 1, 2026, I uninstalled Chrome from my primary desktop and laptop.

My goal: survive two weeks without it, exclusively using alternatives, and document every single friction point, security observation, and productivity hit or gain.

This wasn't about finding a "better" browser in terms of features, but about understanding the real cost of reliance on a potentially compromised system versus the pain of switching.

The Rules of the Test: Going Cold Turkey

To make this a fair, albeit uncomfortable, experiment, I set some strict rules:

1. No Chrome, Period: This meant no opening it "just for one thing." If I caught myself trying to, I had to immediately switch to an approved alternative.

2.

Primary Alternatives: I designated Mozilla Firefox as my main alternative for general browsing and work, and Apple Safari for anything requiring absolute sandboxed security (e.g., online banking, sensitive logins) on my MacBook.

On my Windows machine, I relied solely on Firefox.

3.

Core Workflows: I had to replicate my essential daily tasks: research, writing in web editors, video calls, social media management, email, and interacting with various SaaS tools (CRM, project management, analytics dashboards).

4. Logging Everything: I kept a running log of every instance where the switch caused friction, a security concern arose, or an unexpected benefit emerged.

This included performance observations, extension compatibility issues, and general usability.

5.

Security Focus: While I couldn't "test" the RCE directly (nor would I want to), I would pay close attention to the security posture of the alternative browsers, their update cycles, and any related news.

I logged everything in a simple markdown file, noting the date, time, task, and outcome. The initial days felt like trying to write left-handed after a lifetime of right-handed dominance.

Round 1 — First Impressions: The Ghost in the Machine

Within the first hour of my Chrome-free existence, I noticed something nobody warned me about: the phantom limb sensation.

My muscle memory kept reaching for the Chrome icon, my fingers automatically typing "chr" into the search bar. This wasn't just about a browser; it was about a deeply ingrained habit.

It was honestly a little unsettling how much of my digital life was tied to one application.

My initial setup of Firefox was surprisingly smooth. Importing bookmarks was seamless, and many of my essential extensions (ad blockers, password managers) had direct Firefox equivalents.

Performance felt snappy, perhaps even more so than Chrome, which often felt like a memory hog.

On my older laptop, pages loaded noticeably faster. This wasn't a scientific benchmark, but the subjective experience was immediate and positive.

However, the "first impressions" round wasn't all sunshine.

Some of my niche developer tools, particularly those tied to specific Google services or using proprietary Chrome APIs, simply didn't work as expected or had no direct Firefox counterpart.

For example, a particular analytics debugger I relied on for client work was a no-go.

This meant a minor hit to my productivity, requiring me to find workarounds or use a less efficient method. It highlighted the ecosystem lock-in that Chrome subtly fosters.

The biggest initial security observation was the sheer relief. Every time I opened Firefox, I felt a slight mental weight lifted.

I knew that, at least for now, I wasn't running software with an actively exploited, critical vulnerability that could lead to my machine being compromised by merely visiting a compromised site.

This emotional shift was powerful, underscoring how much background anxiety Chrome’s omnipresence had been causing.

Round 2 — The Deep Test: Real Tasks, Real Pressure

As the two weeks progressed, I pushed Firefox and Safari harder, replicating my most demanding workflows.

This is where the nuances, and the true implications of being Chrome-free, really began to emerge.

Web Development Tools & Compatibility

For someone who works with web platforms daily, Chrome's developer tools are legendary. Firefox's DevTools are excellent, but they have a different workflow.

I found myself relearning keyboard shortcuts and navigating slightly different interfaces.

Debugging JavaScript was a minor adjustment, but CSS inspection felt just as robust. The bigger issue was with websites designed exclusively for Chromium.

A few older client portals, unfortunately, rendered incorrectly or had broken functionality in Firefox.

This wasn't Firefox's fault, but rather a testament to lazy web development, and it forced me to communicate with clients about browser compatibility issues – a conversation I hadn't had in years.

Resource Management & Performance

This was a clear win for Firefox. My laptop, which often sounded like a jet engine with 20+ Chrome tabs open, ran significantly quieter and cooler.

I monitored my RAM usage, and Firefox consistently consumed less memory, especially with multiple tabs and extensions active.

This wasn't just anecdotal; my system's activity monitor showed a consistent 15-20% reduction in browser-related RAM usage compared to typical Chrome sessions.

This translated to better overall system performance, particularly when running other demanding applications like video editing software or local development environments.

Security and Privacy Features

Firefox and Safari both offer robust privacy features, often more aggressively enabled by default than Chrome.

Firefox's Enhanced Tracking Protection blocked a surprising number of trackers that Chrome silently allowed through. Safari's Intelligent Tracking Prevention is similarly powerful.

While Chrome has made strides in privacy, it often feels like an afterthought compared to these browsers, which have built privacy into their core philosophy.

This shift made me realize how much passive data collection I had simply accepted as the cost of using Chrome.

The actively exploited RCE was a wake-up call, but the quiet, persistent tracking was the slow burn.

Extension Ecosystem

While many critical extensions had Firefox equivalents, there were a handful of specialized tools I genuinely missed.

For example, a specific screenshot annotation tool I used daily had a clunky Firefox counterpart. This wasn't a deal-breaker, but it added minor friction to specific tasks.

It highlighted that while the core functionality is there, the long tail of niche tools can be a challenge.

The Results: A Clear Verdict, But With Nuance

After 14 days and countless tasks, the results weren't even close. The decision to step away from Chrome, driven by the actively exploited RCE, revealed a surprising truth:

• Security & Peace of Mind: A dramatic improvement. The knowledge that I wasn't using a browser with a known, actively exploited RCE was paramount. This alone justified the switch. Firefox and Safari both have excellent security track records and faster patch cycles for critical vulnerabilities.
• Performance & Resource Usage: Firefox was the undisputed winner here, especially on my older hardware. My machines ran cooler, quieter, and felt snappier.
• Privacy: Both Firefox and Safari offered superior out-of-the-box privacy protections, blocking more trackers and offering clearer controls over my data.
• Productivity & Workflow: This was the only area with significant friction. While 90% of my workflow transitioned smoothly, the remaining 10% (niche dev tools, Chromium-specific websites) required workarounds or compromises. This wasn't enough to negate the security benefits, but it was a tangible cost.

What This Means For You: Don't Wait for the Patch

If you're still running Chrome, or any Chromium-based browser, right now, you're operating with a known, actively exploited vulnerability. This isn't fear-mongering; it's a statement of fact.

You are literally a target.

• If you handle sensitive data, work with client information, or simply value your digital security: Switch immediately. Firefox is an excellent, open-source choice that offers a familiar-enough interface and robust security. Safari is fantastic for macOS users, especially for banking and sensitive logins.
• If you're a developer or power user reliant on specific Chrome features: Consider a dual-browser strategy. Use Firefox or Safari for general browsing and sensitive tasks, and only open Chrome in a tightly sandboxed environment (like a virtual machine) for the specific, essential tasks that truly require it, and only after ensuring the latest patches are applied. But even then, proceed with extreme caution.
• If you're a casual user: The argument is even stronger. The convenience of Chrome doesn't outweigh the risk of an RCE that can compromise your entire system. Make the switch. It's easier than you think.

Google will undoubtedly patch this vulnerability. They always do.

But the fact that it was actively exploited means that by the time you read this, attackers have likely already refined their techniques or are pivoting to similar flaws.

Waiting for a patch means gambling with your security. It’s an unacceptable risk when viable alternatives exist.

The Twist: Breaking Free From the Default

The biggest surprise wasn't just the relief of enhanced security or the snappier performance of Firefox. It was the psychological shift.

For years, Chrome was simply "the internet." Its ubiquity made it feel like the default, the inevitable choice.

Stepping away from it, forced by a critical vulnerability, was an act of digital liberation.

It made me question other "defaults" in my tech stack, my productivity apps, and even my social media habits.

It's easy to get comfortable with what's familiar, even when it’s silently costing you performance, privacy, or, in this case, security.

The actively exploited RCE in Chromium was a painful reminder that complacency is the hacker's best friend.

It made me realize that sometimes, the best way to secure your digital life isn't to tweak settings, but to fundamentally change the tools you use.

Have you noticed your browsing habits changing since news of the RCE hit, or is it just me? What's your take?

Read Next

Apple Quietly Fixed AirPods' Biggest Flaw. Nobody's Talking About It.

September 10, 2026

Nobody Has Solved Navier-Stokes

September 10, 2026

Gary Gallagher: American Civil War, Slavery, Lincoln, Grant & Lee | Lex Fridman Podcast #499

September 10, 2026