I'm not joking. You can see other replies for details lists of functionalities and capabilities often pioneered and supported by Safari long before other brows

I'm not joking. You can see other replies for details lists of functionalities and capabilities often pioneered and supported by Safari long before other browsers (even Firefox). Some loud voices from the community have very selective memory, and they momentarily forget all the evilness pumped into Chrome regularly. (remember FLoCs? Advertising API? AMP?) All that hate for Safari can be much more productive if channeled as constructive feedback on browsers' bug trackers and governance discussions, improving the ecosystem as a whole (which is what you want if you care for the web). Such conversations can even lead to the natural evolution of standards and implementations towards more refined engine customizations on each platform. Today, iOS allows for open browser choice on iOS, so any technical requirements for the implementation are of no meaningful consequence to iOS users. Everyone can get the look, feel, and service integration with their preferred vendor's ecosystem. Consumers and developers also get a consistent experience throughout the entire operating system - a piece of content will appear the same in any context. Simple, efficient, and reliable. All this will be lost the moment someone decides to prop a "To view this website, download browser XYZ." Imagine you are faced with this in a stressful situation when you need your phone to work the most.