Today, iOS allows for open browser choice on iOS, so any technical requirements for the implementation are of no meaningful consequence to iOS users. Such conversations can even lead to the natural evolution of standards and implementations towards more refined engine customizations on each platform. (remember FLoCs? Advertising API? AMP?)Īll 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). Some loud voices from the community have very selective memory, and they momentarily forget all the evilness pumped into Chrome regularly. You can see other replies for details lists of functionalities and capabilities often pioneered and supported by Safari long before other browsers (even Firefox). and the devtools are still far behind chromes.ĪV1/AVIF and VP8/VP9/WebP (Open Media Codecs) Huge numbers of bugs (some of which haven't been fixed in over 7 years)ĥ. Doesn't really support Web Apps, no user findable method of install (install prompts), no push notifications.Ĥ. In the MDN developer Survey developers ranked Safari as the second biggest problem after IE. 360 related to Safari, compared to 30 for chrome and 10 for firefox.ģ. In State of CSS last year had the most number of complaints in relation to bugs. Safari, performs worst on wpt.fyi by a VERY wide marginĢ. You've got be joking right? ok so lets go through some stats:ġ.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |