I can understand choosing not to support it. Safari is frustrating to web developers because you can't legally test on it without owning Apple hardware. Whereas Microsoft provides free virtual machines for testing on its browsers. I've done the same thing on my personal sites - I've outright blocked Safari with a message explaining that I won't unblock it until Apple provides a Safari VM.
They used to provide builds of Safari and Webkit for Windows; people complained endlessly about the very fact of their existence. Apple stopped providing them. True story.
Also, outright blocking Safari users is sort of obnoxious.
Sorry but that's not even remotely close to being the same. The Windows builds were notoriously badly supported and were never equivalent from a debugging perspective. Microsoft made a genius move by providing its IE VMs, and if Apple didn't want to force developers into its ecosystem they'd have done the same.
I agree that it's obnoxious, but I'd rather do that than deal with Safari users complaining about bugs on my sites that I have no intention of buying a Mac or breaking the law to fix. I'd rather avoid the bug reports and let the users know that it's Apple fixing it. The sites I run are entirely free and paid for out of my own pocket anyway, so I don't want my money going towards people who support Safari. I've considered blocking Chrome, too, for other reasons.
