Apple's new 'Switch to Safari' campaign details why you should ditch Chrome

Original Article ↗ Hacker News Discussion ↗

Apple’s new “Switch to Safari” campaign urging users to abandon Chrome has reignited long‑running debates over browser power, privacy, and web standards. Commenters weigh Safari’s performance and battery advantages against its weak dev tools, PWA limitations, and Apple’s iOS engine lock‑in, while warning that Google’s dominance with Chrome risks turning the web into a de facto “Chrome platform.” Many argue the healthiest outcome isn’t mass migration to Safari but greater use of independent engines like Firefox to preserve real browser diversity.

Overall sentiment on Chrome

  • Many agree Chrome should be ditched, citing tracking, enshittification, MV3 limitations, and Google’s outsized control over web standards.
  • Some users remain “perfectly happy” with Chrome, often due to reliability with complex sites like YouTube and corporate defaults (Edge/Chrome).

Perceived strengths of Safari

  • On macOS, Safari is praised for speed, low RAM usage, and especially battery efficiency.
  • Tight OS integration, native look-and-feel, and “just a browser, not an OS” philosophy appeal to some.
  • Considered an important non‑Chromium engine helping prevent total Google control of the web.

Major criticisms of Safari

  • iOS: all browsers must use WebKit, seen as a de‑facto engine monopoly and a way to protect App Store revenue, limit PWAs, and block powerful web APIs.
  • Cross‑platform: no official Safari on Windows/Linux/Android; testing requires Apple hardware or workarounds.
  • Features: weak or awkward dev tools, limited extension ecosystem, no easy custom search engines, clunky vertical tabs, odd UX (e.g., “Find in page,” history placement, animations).
  • Compatibility: many report Safari‑only rendering bugs, PWA breakage, and sites that perform worse than Chrome.

PWAs and web capability concerns

  • Apple is accused of intentionally hobbling PWAs (install flow, storage limits, missing APIs, 7‑day data expiry historically) to protect native apps.
  • Some note partial improvements but still describe installation and notifications as high‑friction and fragile.

Browser diversity vs user choice

  • One camp: Safari’s engine lock on iOS is justified as a necessary counterweight to Chrome monoculture and lazy “Chrome‑only” development.
  • Opposing camp: this is just Apple replacing one monopoly with another, harming users and developers and holding back web standards.

Extensions, ad blocking, and MV3

  • Full uBlock Origin not available on Safari; uBlock Origin Lite and Safari‑style content blockers (1Blocker, Wipr2, AdGuard, etc.) exist but are seen by some as weaker.
  • MV3’s constraints and Safari’s similar limitations are viewed as harmful to effective ad blocking; others claim practical differences are smaller than often portrayed.

Alternatives and personal choices

  • Many recommend Firefox (often with uBlock Origin) as the primary Chrome alternative.
  • Brave, Vivaldi, Edge, and niche browsers are mentioned for specific strengths (privacy, customization, better YouTube behavior).
  • Several users mix browsers: Safari for light/personal use, Firefox or Chromium for problematic sites.