Google's Chrome antitrust paradox

Chrome, Web Standards, and Browser Monoculture

• Many see Chrome as having “won” by rapidly implementing features (sometimes before standards are settled), forcing others to follow and effectively steering the standards.
• Critics say Google ships under‑specified or non‑standard APIs (especially some hardware/PWA, Background Sync/Fetch, Constructable Stylesheets), creating de‑facto standards and fragmenting the web.
• Defenders point to Chrome’s documented, public feature‑launch process, origin trials, and involvement in W3C/WHATWG as evidence of a relatively disciplined, transparent approach compared to earlier eras.
• There’s disagreement over history: some say the web always evolved via browsers racing ahead with features; others emphasize the value of slower, consensus‑driven standards.
• Multiple comments worry that Chrome/Chromium dominance makes independent engines (like Firefox/WebKit) hard to sustain; the “standard” risks becoming “whatever Chrome does.”

Antitrust Theories and the Paper’s Remedies

• Some readers find the paper’s case for spinning off Chrome weak: many examples (DNT failure, Widevine, self‑preferencing via Chrome popups) are seen as tied more to Google Search/ads than to browser ownership per se.
• Others argue that separating Chrome could reduce internal conflicts of interest and accusations of self‑dealing, though funding and incentives for an independent browser are unclear.
• Discussion contrasts EU focus on harm to the marketplace vs US focus on consumer harm; this affects whether a dominant but popular browser is viewed as an antitrust problem.
• Debate over whether ~65% share (plus Chromium‑based competitors) is functionally a monopoly.

Ads, Privacy, and Tracking (FLoC, Topics, Privacy Sandbox)

• One camp views FLoC/Topics and Privacy Sandbox as Google using Chrome’s dominance to replace third‑party cookies with a Google‑designed system, locking in an advantage while marketing it as “privacy.”
• An ad‑tech practitioner counters that Chrome privacy work is separated from Google Ads, under regulator oversight, and that Sandbox is tested with multiple companies and aims to reduce PII exposure.
• Critics call Sandbox a “dark pattern”: the browser infers interests and shares them with sites by default, with confusing opt‑outs; they argue a true “privacy sandbox” would simply block tracking entirely.
• Broader concern: Chrome’s integration with Google accounts, delayed 3P cookie deprecation, manifest v3 limits on ad blockers, and moving services under google.com subdomains all tilt the playing field toward Google’s ad stack.

DRM (Widevine) and Platform Power

• Some say Google’s control of Widevine (dominant web DRM used in Chrome) lets it gatekeep which new OSes/platforms can get major streaming services, potentially harming competition.
• Others respond that multiple DRMs (PlayReady, FairPlay, etc.) exist and that Widevine actually simplified a previously worse, fragmented DRM world; even Mozilla relies on it.

Conflict of Interest and Source Skepticism

• A co‑author’s employment at a Google competitor prompts debate: some see non‑disclosure as a serious lapse, others say the work was done independently and that such affiliations don’t automatically invalidate arguments.
• Several stress focusing on concrete evidence of bias or errors in the paper rather than affiliations alone.

User Experience, Alternatives, and “Dark Patterns”

• Some Mac users say Chrome is essential and keeps the web “open” against Apple’s restrictive Safari and App Store model; others report Safari/Firefox work fine and note Chrome’s heavy resource use and tracking.
• There’s frustration about persistent Chrome install prompts on Google properties and automatic Chrome profile sign‑in; whether these are “dark patterns” or just aggressive marketing is contested.
• Complaints about AMP degrading UX on non‑Chrome browsers, and allegations that some Google services perform worse on Firefox/Safari unless user agents are spoofed.