As a Gen X dev who had to grapple with IE6 back in the day, and worked at a FAANG where things had to work for everyone, Safari really is pretty bad. (And I wish it weren’t the case since WebKit was a major advance at the time).

The thing about Safari bugs these days is how they’re really obscure, and that once you find them, they’re total blockers with no workarounds.

Since all the vendors are much more on board with standards now, there aren’t as many hacks for targeting a specific browser (which is a good thing), which means that if just one of the vendors gets it wrong, you can’t use the API/property/method/whatever until the vendor fixes it. Or you just let it be broken in that browser (which is how it should be).

Safari plus web components, shadow DOM, logical properties, and PWAs is a godawful mess.