In a surprising turn of events, David Heinemeier Hansson, the renowned creator of Ruby on Rails, publicly opposed a U.S. Department of Justice (DOJ) proposal that could force Google to sell its Chrome browser. While antitrust regulators aim to reduce Google’s dominance in search and online advertising, Hansson believes that such a move could severely damage the open nature of the web. His blog post raises important questions about what truly constitutes a monopoly, and whether breaking up Chrome would serve users—or harm them.
In this post, we’ll explore the core of Hansson’s arguments, why he believes Chrome’s dominance is different from the monopolistic control exercised by mobile app stores, and how forcing a sale could ironically centralize power rather than distribute it. We’ll also discuss what this means for web developers, internet users, and the future of browser innovation.
The DOJ’s Antitrust Proposal: What’s Happening?
The DOJ has intensified scrutiny on Google’s business practices, focusing particularly on its control over digital advertising and search. One of the most drastic suggestions from regulators is to break up parts of Google’s empire, including the Chrome browser, which currently leads the browser market by a significant margin.
The concern is that Chrome, by being the dominant browser, gives Google unfair leverage to maintain its supremacy in search and advertising. By owning the browser, the search engine, and the ad platforms, critics argue, Google has too much influence over how people access and interact with the web.
David Heinemeier Hansson’s Unexpected Stance
David Heinemeier Hansson (often referred to as DHH), is no stranger to advocating for open standards and criticizing tech monopolies. That’s why his strong opposition to the idea of selling Chrome caught many by surprise. In his personal blog, DHH expressed deep concern, stating:
“The web will be much worse off if Google is forced to sell Chrome.”
This stark warning stems from his belief that Chrome, despite being a market leader, earned its position not through coercion, but through superior technology and performance. According to DHH, Chrome’s rise pushed the entire web ecosystem forward—by promoting modern web standards, speeding up the adoption of new technologies, and making development more consistent across platforms.
Chrome’s Influence on Web Standards
One of Hansson’s key arguments is that Chrome’s dominance has driven much-needed progress in web development. Before Chrome’s rise, developers had to deal with severe inconsistencies across browsers, with Internet Explorer being notoriously difficult to work with.
Chrome introduced faster rendering, more frequent updates, and strong developer tools, setting a high standard that others were compelled to follow. It also championed open-source technologies, through the Chromium project, which powers browsers like Microsoft Edge, Brave, Opera, and others.
Hansson notes that this influence is not inherently bad. In fact, it has helped unify the web, making it easier for developers to build robust applications and for users to have consistent experiences across devices.
Alternative Browsers Still Exist
Another point DHH emphasizes is that Chrome is not the only option. Users can still choose Firefox, Safari, and other Chromium-based browsers. The fact that people continue to use Chrome in such large numbers is, according to him, more a testament to its quality than a symptom of monopolistic behavior.
Moreover, Chrome itself is based on Chromium, an open-source project that is freely available. This means competitors can—and do—build their own browsers using the same underlying technology. In other words, Chrome has contributed to a broader ecosystem rather than stifling it.
The Real Threats to Web Openness: App Stores
DHH draws a sharp contrast between Chrome’s market share and the control exercised by app stores like Apple’s App Store and Google’s Play Store. These platforms not only control distribution but also enforce strict policies and take substantial commissions from developers.
He argues that these walled gardens represent the true monopolistic threat. If the web were to become less relevant, and more services moved to mobile apps controlled by these stores, we would see even less openness and fewer user rights. In his words, ecosystems like the App Store are “genuinely harmful.”
This highlights a central irony: while the DOJ is targeting Chrome in the name of competition, it may be ignoring or underestimating the larger threat posed by mobile gatekeepers who don’t allow the same freedom as the web.
A Balanced View on Google’s Power
To be clear, DHH is not defending all of Google’s practices. He explicitly states that Google should not be excused from manipulating the digital advertising market or using anti-competitive tactics. However, he believes that forcing Google to sell Chrome would be a step too far—one that damages the web as a whole rather than just Google.
By breaking apart the teams responsible for Chrome and separating them from Google’s infrastructure, updates might become slower, innovation could stagnate, and the collaborative ecosystem currently built around Chromium could be fractured.
Implications for Web Developers and Users
For web developers, a stable, standards-driven environment is essential. Chrome’s leadership, though not perfect, has offered predictability and power tools that make development smoother. Losing that cohesion could mean a return to the days of fragmented browser experiences and compatibility headaches.
For users, fewer updates or inconsistent security practices could mean a less safe and reliable web. And if the browser market becomes unstable, there’s a risk that more companies will push users toward closed platforms—reducing web usage in favor of controlled, app-based experiences.
Conclusion: A Call for Nuance in Regulation
David Heinemeier Hansson’s blog post is a call for nuance. While holding tech giants accountable is essential, not all dominance is created equal. Chrome’s leadership, according to Hansson, has helped improve the web—not hurt it. Regulatory efforts should focus on actual anti-competitive behaviors and harmful monopolies, like those enforced through app store gatekeeping, rather than dismantling the tools that have made the open web more powerful.
As the debate around Google, Chrome, and online dominance continues, it’s important to ask: will our actions make the web better—or risk breaking what’s already working?
What’s Your Take?
Do you agree with DHH that forcing Google to sell Chrome is a mistake? Should regulators focus more on app stores instead?
