I'm sure it's fine for casual users, and you can't deny the battery life improvements when using Safari.
However as I posted in another comment, Safari is the new IE when it comes to bugs and standards compliance.
Here's an example that broke many many sites that use OAuth2 Auth Code Flow for login (including the main UI portal my company provides clients): https://bugs.webkit.org/show_bug.cgi?id=194906
This was also an issue in iOS, and since Apple doesn't let any other browsers actually use their own rendering engine on that platform (they're just wrappers around Safari's guts) this was broken for all iPhone users no matter the browser.
This is just one example. There's been numerous other issues such as disabling third party cookies by default.
I can only surmise that Mac users use Chrome/FF because the internet just _works better_ when they do.
However as I posted in another comment, Safari is the new IE when it comes to bugs and standards compliance.
Here's an example that broke many many sites that use OAuth2 Auth Code Flow for login (including the main UI portal my company provides clients): https://bugs.webkit.org/show_bug.cgi?id=194906
This was also an issue in iOS, and since Apple doesn't let any other browsers actually use their own rendering engine on that platform (they're just wrappers around Safari's guts) this was broken for all iPhone users no matter the browser.
This is just one example. There's been numerous other issues such as disabling third party cookies by default.
I can only surmise that Mac users use Chrome/FF because the internet just _works better_ when they do.