Apple's new 'Switch to Safari' campaign details why you should ditch Chrome
- ID
- 35352
- Status
- summarized
- Published
- 13 Oct 2026, 10:26 PM
- Fetched
- 14 Oct 2026, 9:59 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://9to5mac.com/2026/10/12/apples-new-switch-to-safari-campaign-details-why-you-should-ditch-chrome/
- Source URL
- https://hnrss.org/best
Summary
- Score
- 3.0
- Created
- 14 Oct 2026, 10:01 PM
- Tags
- Audience
- developers
What happened
Apple launched a 'Switch to Safari' marketing page plus two YouTube videos (covering Distraction Control and Intelligent Tracking Prevention) claiming Safari is 'a more powerful and private browser than Chrome.' The page asserts specific numbers — up to 5 hours more video streaming on Mac versus Chrome, and up to 35% faster loading of frequently visited sites — alongside a side-by-side comparison chart and features like Reader Mode, Notify Me, Profiles and Apple Pay. It follows an earlier 'Privacy on iPhone' campaign from this year; the top HN comment argues the campaign is wasted effort unless Apple brings Safari back to Windows.
Why it matters
The '5 hours' and '35% faster' figures come with no published methodology or test conditions in the article, so treat them as vendor claims rather than benchmarks — if you cite browser performance or privacy in a pitch or migration decision, don't repeat these numbers without your own measurement. For anyone shipping web apps, the practical item is the browser mix you test on: this is a consumer-marketing push, not a WebKit change, so nothing in your stack needs to change this week.
Discussion angle
Apple published headline performance numbers ('up to 35% faster') with no methodology attached — is there any case where a vendor's own benchmark is good enough to act on, and how would you cheaply reproduce that test on your own sites?