Ok that's fair. From a developer's PoV, Safari is a terrible browser. It's old and buggy and stifles innovation on iOS in the same way ie did on windows.
As a web developer, I find this to be anything be true. Safari supports loads of cool features that clients ask for, like native css carousels (css snap points), and blur effects (backdrop-filter). Chrome, does not.
As a web developer, I like my browser to implement internet standards correctly so websites actually work. People aren't trashing Safari because it's cool.. generally Apple provides a great software experience. But Safari is a bug ridden mess.
Here's an example that broke many many sites that use OAuth2 Auth Code Flow for login (including the main UI portal my company provides clients): https://bugs.webkit.org/show_bug.cgi?id=194906
There's also been issues with the handling of 3rd party cookies that create issues for login systems, js stdlib functions being incorrectly implemented, etc.
Safari generally implements standards as they mature.
Chrome generally implements everything new and shiny, no matter how underspecified it is, and with blatant disregard to whether or not it breaks the web.
I don't disagree with regards to new standards, but that doesn't change the fact that existing, well established standards are often broken in Safari (see the bug I linked in the parent comment). These bugs are much more likely to break the web than Chrome's half baked bleeding edge features because there's already a huge body of web software that relies on them.
Software has these everywhere. iOS and Android homescreens are carousels. Netflix 'rails' are carousels. CSS Snap Points is a way to create native snapping scrolling views, which Safari and IE supports, but Chrome does not.