Why Google Chrome Sucks For Web Development

Sarah Kohavi -

When the mighty Google was first founded, its motto was "don't be evil" Initially, we believed this, but at some point, Google quietly pulled out a jackhammer and ripped it off the wall without anyone noticing.

Using Firefox: Debug Websockets with Ease and Elegance.

Using Chrome: Sacrifice a goat, chant the devtools incantation, and hope the page loads.

What is Firefox?

Originally released November 9th 2004 (Almost old enough to drink in the US at the time this article was written) by the Mozilla Foundation. Mozilla Firefox has been a free and open source alternative to Internet Exploder (sorry... Explorer), Netscape Navigator, and Opera. Getting with the times now, Firefox competes with Edge and Chrome.

What does FireFox have to Offer?

  • For one, FireFox offers an intuitive interface. It's portable and lightweight, and it supports Container-Tabs.
  • FireFox also provides cleaner DevTools, cleaner workflows when working with Websockets, Stylesheets, Code Injection, and JSON.
  • FireFox’s DevTools for Websockets is much cleaner.
  • Firefox also supports a neater development flow when working with responsive devices

Why Not Chrome?

  • Made by Google, Google's track record for throwing an immense plethora of crap at the wall and seeing what sticks is just disconcerting and shows a lack of fore-planning and professionalism.
  • Chrome eats RAM like your weird uncle hogs the thanks giving turkey.
  • Lacks container-tabs.
  • Stupidly complex workflow for testing small resolution screens in responsive web design with touch disabled devices.
  • Chromium has further reduced the add-on API to restrict and counteract Adblockers
  • Overhyped

Chrome's Crimes Against Humanity

  • Add-on Manifest V3 rendering a user's right to opt out of intrusive advertisements about Viagra virtually impossible. 2023 - June 2025 [Source]
  • Originally, Device Mode was more prominently visible in Dev Tools, but it's now hidden away and requires the user to create "Device Profiles" rather than easy, free-form responsive control.
  • Even after 16 years, Chrome still can't do container tabs... WHY?!
  • In 16 years, Chrome still hasn't sorted its sh*t out and dealt with the memory issues. This is much more impactful now, considering the impact on mobile device batteries.
  • It's no secret. We know that Google collects data. But it's what Google never tells us it's doing with our data that bugs the crap out of us! Even in Incognito mode, leading to a $5bn lawsuit being settled by Google in 2024. [Source]

Google Chromes only redeeming feature is that it's not Microsoft Edge...