Supporting multiple browsers is a uniquely annoying aspect of web development, and almost every developer uses Chrome for development (I’m a Safari user and it’s kind of a running gag at work). This means that for most developers, Safari is the main browser they have to support that isn’t the one they use for development, which is a recipe for resentment.
Also, I bristle at this comparison a bit because Safari is wayyyyy better than IE ever was about adopting (and helping to draft) standards. They’re slower than the Chrome team and adopting new standards, but that’s because Alphabet and Apple’s business models are different, not because it’s an inherently good idea to adopt every new standard immediately (especially when many are focused on turning the web into a crappy replacement for native app platforms).
On Safari (both iOS and OS X) Safari does not support grid-gap, i.e. "gap" CSS property.
https://developer.mozilla.org/en-US/docs/Web/CSS/gap#support...
I use the fullscreen API to give prototype demos of a product to clients, and iOS [iPhone] Safari doesn't support the fullscreen API.
https://developer.mozilla.org/en-US/docs/Web/API/Fullscreen_...
As someone who does not primarily do web development... no. No I do not :). I am trying to get it to do what I want in Chrome and I find I hate it only slightly less than older CSS.
Anecdotally, friends have told me I shouldn't use grid, I should use flexbox instead.
Clearly I'm not meant to be a web developer. Some people like it, I gather.