Safari is the new IE
There is a really good center of the road set of web browser features which all modern browsers support. This was not the case when IE was big, in order to make nice, functional web pages you needed to either give up supporting one platform or the other or you needed to spend tons of time and energy making 2 (or 3) pathways for extremely basic features.
If one browser is 1 year or two behind standards generally doesn't matter because as web developers we need to support 3-4+ year old browsers regardless. The truly crappy thing about IE was that Microsoft had zero commitment to web standards at all and many things they did outright contradicted them. Since IE had such massive market presence they undermined the standards process for more than a decade.
On the project I currently work on the codebase is _littered_ with workarounds and hacks to get stuff to work on Safari.
Again, this is nonsense.
There is a gap, but it's not bending the shape of the web or costing the average developer hundreds of hours to work around bullshit. Safari is behind on some features... no doubt at all. But to compare that to IE 6 is just wrong.
Safari for iOS (and Apple in general) is bending the shape of the web. For example the poor support for PWAs.
Rather than targeting your frustration towards developers who don't want to or have the time to bend over backwards to accommodate terrible browsers, how about directing that energy towards encouraging those browsers to catch up and stop holding back the web?
I’ve had issues with canvases just sort of “flashing” for no reason, and if you try to use SVG filters or other parts of the SVG standard that have been standardized for years... well Safari doesn’t choose to just ignore them. Instead it will sometimes just make the parts of the SVG affected by the filter turn black and then call it a day.
So I wouldn’t say that it’s as easy to create something that works fine in Safari and breaks in Chrome. Making something that works in Safari is just plain hard.
Safari also basically destroyed my animation whenever the window size was changed, which also applies to switching from portrait to landscape on iOS.
>The downvotes are happening because this would have been as possible to achieve in Safari as in Chrome had the author chosen to develop purely in that, and Chrome would have been one of the engines that look broken.
This is not true.
>At this level you’re relying on engine quirks rather than spec compatibility.
I think you're misunderstanding - the art was developed with standards. Safari is the piece that is failing the standards, not the art.