Comment on Here we go again
SnowdenHeroOfOurTime@unilem.org 1 year agoInteresting. I didn’t know that. Safari is a piece of shit for other reasons too
Comment on Here we go again
SnowdenHeroOfOurTime@unilem.org 1 year agoInteresting. I didn’t know that. Safari is a piece of shit for other reasons too
Reygle@lemmy.world 1 year ago
Example reason why Safari is shit: It’s Safari
SnowdenHeroOfOurTime@unilem.org 1 year ago
Yeah. They selectively adopt web standards years later than the others and the mobile and iPad versions in some ways behave completely differently from desktop (and each other). If safari just acted like the other browsers, frontend web dev would be MUCH easier.
SpeziSuchtel@feddit.de 1 year ago
Depends on which standards, for some css functions like backdrop-filters and mix-blend-modes it was years ahead of Firefox, where some of those had to be activated through about:config. I‘m glad Firefox catchend up in the past few years though. Also WebKit accelerated HTML5 adoption a lot.
SnowdenHeroOfOurTime@unilem.org 1 year ago
I feel like you’re referring to Firefox literally 12 years ago or more. I’m talking about today. Literally any brand new standard is not supported for 1-2 years minimum. I run into problems with safari on a near daily basis. I rarely have a weird issue in Firefox. 99% of the time chrome and Firefox behave the same. The vast majority of the time that one browser has an issue others don’t, it’s safari. It’s weird to me to get pushback on this …