I think the title is right, but mainly because of the multitude of Safari bugs and its incredibly slow performance. This is for Safari of OS X: assuming it does

I think the title is right, but mainly because of the multitude of Safari bugs and its incredibly slow performance. This is for Safari of OS X: assuming it doesn't crash on startup (so for me, about two out of three computers these days, up from one out of three), Safari is a piss poor browser even when it manages to run. I have a lot of code that runs incredibly slow on Safari yet has no problems in other browsers. Sometimes it drops connections randomly. Sometimes pages just crash. Sometimes it just won't render anything. The exact same code works fine in Chrome, FF, etc. and is pretty typical angular code. In other words, it's cross-browser code. Luckily, I don't think we have many Safari customers and at this point, if things don't work in Safari, the bugs I find are filed with the lowest precedence (ie: they will never get fixed) and that only because we have a person on our team who insists on using this broken browser. The lack of support for the APIs mentioned in the article only serves to drive the point home for me. The developer tools are also substandard compared to either Chrome or FF. IE at least had market share. There is nothing that makes developing for Safari (OS X) worth the time spent.