How have you not noticed any of them? Most obvious is local storage throws out of space exceptions if Safari is in private mode. I'm not even a web developer.
Re:Safari no longer supported by Spotify
by madeofpalk on Sunday September 17, 2017 @12:54PM
(#15270485)
Honestly, not really. The only one I can think of is your localStorage example.
Regardless, that's not the point. I'm not saying that Safari is perfect, I'm just saying that while it might have some implementation differences and bugs, so do other browsers.
No service workers, web rtc, Stream API or any other feature that can make web apps a viable replacement to app store installed native apps.
Re:Safari no longer supported by Spotify
by rmwaite on Sunday September 17, 2017 @11:38PM
(#15273237)
As of iOS 11 and macOS 10.13 Safari does support WebRTC and streaming API. And I don't see them supporting service workers any time soon because that's a stupid fucking idea.
Re:Safari no longer supported by Spotify
by madeofpalk on Monday September 18, 2017 @06:06AM
(#15274580)
Clients ask me to develop carousels much more than I'm asked to make a P2P video conferencing app.
Re:Safari no longer supported by Spotify
by coldtea on Sunday September 17, 2017 @12:06PM
(#15270241)
Because private mode is for porn? Who'd try normal apps there?
(only kidding, but it's not the most obvious thing to check and optimize for if you're a web dev. If that's what Safari's problems are, it's pretty solid.)
I look at Firefox and some of it's inconsistent behaviours around flexbox compared to other browsers (mind you, some of these are due to the spec). Just today I had an irritating render bug in Chrome.
I know, this all comes down to hearsay and individual experiences. But I still strongly believe that 'Safari is the new IE' is nothing but baseless FUD.