What Do Front-End Devs Think About Safari?

I'm mostly a back-end guy, and have by and large worked with Firefox and Chrome being the browsers of choice, and have only had two issues with Safari (see below). As of today, I may have a third, but I may just have a configuration issue. So, please, what do you think about Safari? Is it the new IE 6? Is it considered decent? What do you think?

• Look at this URI: http:/~foo/ It's wrong. You stick it in the browser and it doesn't work, but put it in a page and it will just assume the current server. It's just one step away from /~foo/, right? At least that's the logic my coworker had, but it broke the page for some users. When I had this issue in 2012, it worked in Firefox and Chrome and Opera and IE, but, I figured out by the logs, not Safari. The issue is that every other browser supported it I don't know if they still do and Safari didn't.

• HTML5 added an Audio API. To learn it, I created a page where, when you go there, you got an old-school pre-VOIP dial tone, which is actually two tones. But the Secret Masters of HTML decided that pages making noise without us saying "you can make noise" is a bad thing, and so I rewrote it so that, and I asked my wife to check on the iPhone and it wouldn't play. I never fully figured out the issue between iOS Safari and my HTML5 stuff, but I installed a WebKit-based browser on my Linux box to try to work it out, and I don't believe I ever fully did.

So, that's my bits. What do you think about Safari? Do you have any Safari stories?