News for hackers. Stuff that matters.
Re:Apple's new 'Switch to Safari' campaign details why you s... by edoceo on Tuesday October 13, 2026 @07:11PM (#50080261)
There are three choices: use Safari for sub-par site experience, use Chrome for compatible, don't use the site.
Re:Apple's new 'Switch to Safari' campaign details why you s... by simondotau on Tuesday October 13, 2026 @07:15PM (#50080301)
Yes, except the Safari experience is only sub-par because the developer chose to use some bleeding edge feature that doesn't fall back gracefully, or is relying on a Chrome bug, or a lax feature implementation in Chrome.

There's no reason for Safari to have a sub-par experience except for the laziness of some web developers.

Re:Apple's new 'Switch to Safari' campaign details why you s... by doginasuit on Tuesday October 13, 2026 @07:51PM (#50080594)
> There's no reason for Safari to have a sub-par experience except for the laziness of some web developers.

How about a browser with a captive userbase that has less incentive to stay up to date with web standards?

Your argument is that we should expect developers to target/test their app on many different browsers where any random CSS property behaves differently. They will have to buy a device just for this purpose. Because it is obviously developers who should have to pick up the slack here, not Apple.

Re:Apple's new 'Switch to Safari' campaign details why you s... by ryandrake on Tuesday October 13, 2026 @09:44PM (#50081378)
Developers should develop for the web, not one particular browser. There are desktop and native mobile applications that manage to work across multiple operating systems and cpu architectures, and you’re telling me web developers can’t test their shit on a handful of browsers and configurations?
Re:Apple's new 'Switch to Safari' campaign details why you s... by Rohansi on Wednesday October 14, 2026 @12:58AM (#50082571)
You're correct but it's not always this simple. Apple drags their feet with the implementation of some standards and sometimes there is nothing to fall back on. Many of those standards are just bringing functionality available in native apps to the web so we can only speculate that they do it to keep apps on the App Store. One good example is push notifications: they took a long time to support it, and the "Add to Home Screen" requirement makes it almost worthless.
Re:Apple's new 'Switch to Safari' campaign details why you s... by simondotau on Wednesday October 14, 2026 @09:34AM (#50087569)
That’s not a good example, that’s literally the worst example you could have possibly chosen. Push notifications are an anti-feature. It is a disgusting embarrassment that they were ever considered part of the web platform, and I admire Apple for rightfully resisting it.

Safari is a better browser because it doesn’t support them.

Re:Apple's new 'Switch to Safari' campaign details why you s... by Rohansi on Wednesday October 14, 2026 @10:16AM (#50088121)
I see that reaction a lot but it doesn't make sense to me. Yes, there are apps that abuse them, but that is why it requires your permission. Exactly like how native apps require your permission to send you push notifications. So why are push notifications only acceptable in native apps?

> Safari is a better browser because it doesn’t support them.

It has supported them since iOS 16.4. The issue is they made enabling them so high friction for users that you're better off publishing a WebView wrapper to the App Store instead. More work for app devs, worse experience for users, but great for Apple because it's still on the App Store.

Re:Apple's new 'Switch to Safari' campaign details why you s... by crab_galaxy on Tuesday October 13, 2026 @07:32PM (#50080436)
100vh, PWAs, and full screen support that isn’t absolute garbage aren’t exactly bleeding edge features
Re:Apple's new 'Switch to Safari' campaign details why you s... by simondotau on Tuesday October 13, 2026 @07:42PM (#50080507)
Being able to block trackers and not use ridiculous amounts of RAM aren't exactly bleeding edge features either