Maybe one of the websites you use frequently doesn't have good support for WebKit. They make sure Chrome works, and often test Mozilla, but 80% of the time they roll out a new feature it's broken in WebKit for a couple of weeks before the devs fix it. Yeah, you'd like to go to a different website, but you've had an account on this one for over a decade and know a lot of other users, or they get scoops that none of their competitors do, so that's just not going to work for you.
Or, the other browser implements part of the `webext` API that WebKit does not, and there's an extension out there that you'd really like to use. Maybe one that integrates with your existing password manager, or rewrites Twitter URLs to nitter.net, or whatever, and the extension just won't work with WebKit.
Or, maybe WebKit's JavaScriptCore just isn't fast enough for some web-based game you like, and you'd like to run a browser that uses V8 or SpiderMonkey instead.
You're right, a lot of users don't have these problems, and don't care... until maybe one day they do. And maybe 99% of users will never have these problems at all, but 1% of Apple's userbase is still a lot of users who could benefit from browser choice, one day.
Or, the other browser implements part of the `webext` API that WebKit does not, and there's an extension out there that you'd really like to use. Maybe one that integrates with your existing password manager, or rewrites Twitter URLs to nitter.net, or whatever, and the extension just won't work with WebKit.
Or, maybe WebKit's JavaScriptCore just isn't fast enough for some web-based game you like, and you'd like to run a browser that uses V8 or SpiderMonkey instead.
You're right, a lot of users don't have these problems, and don't care... until maybe one day they do. And maybe 99% of users will never have these problems at all, but 1% of Apple's userbase is still a lot of users who could benefit from browser choice, one day.