Oddly enough I went back to using Safari on MacOS. Battery life was big reason. The other was safari has been the only browser I can get to successfully stop playing video ads.

People are not used to Safari breaking regularly, that's absurd. But it's probably easier for them to run a second browser to work around broken sites than it is to figure out how to complain to the site. And having your site be broken reflects badly on you, not on Safari.

Safari's JS support is pretty good, but CSS is wonky and various other things (like how cookies are handled) are different than all the other major browsers. So it will break on shit devs may not expect. Obviously that's the fault of the devs (IE10/11 are worse, but we make stuff work there too!), no argument there.

But it is becoming a pretty niche browser, and yes, it DOES break a lot of stuff. No, it's not broken on Facebook or your favorite news site, but every time I bring it out for a test drive I find a couple of broken things in various smaller web apps that work everywhere else.

So while I don't think it should be that way, it tends to be a pretty brittle experience.

I work on desktop and switched to Safari because Chrome is bloated and slow. Also Safari's tabs UX is much better.

Opening Chrome once a week because some site works only in Chrome is really easier than bothering to file tickets.

I don't find Safari inconvenient at all. Its UI is lean, the default key bindings are nice, and with sVim it's even better.