# Safari's approach may push web developers and users toward Chromium

DevFeed: [Safari's approach may push web developers and users toward Chromium](<https://devfeed.tech/articles/safari-isn-t-protecting-the-web-it-s-killing-it-19095.md>)

Original publisher: [Read original article](<https://httptoolkit.com/blog/safari-is-killing-the-web/>)

Author: HTTP Toolkit; Tim Perry

Published: 2021-07-28T15:50:00Z

Content type: opinion

Language: en

Sources: [HTTP Toolkit](<https://devfeed.tech/sources/http-toolkit.md>)

Topics: [browser](<https://devfeed.tech/topics/browser.md>), [Web](<https://devfeed.tech/topics/web.md>), [Chromium](<https://devfeed.tech/topics/chromium.md>), [WebKit](<https://devfeed.tech/topics/webkit.md>)

Tags: [apple](<https://devfeed.tech/tags/apple.md>), [browser](<https://devfeed.tech/tags/browser.md>), [browsers](<https://devfeed.tech/tags/browsers.md>), [chromium](<https://devfeed.tech/tags/chromium.md>), [safari](<https://devfeed.tech/tags/safari.md>), [web](<https://devfeed.tech/tags/web.md>)

## AI overview

This opinion article argues that Safari's unimplemented features, bugs, and slow release cycle can harm web development and may push developers and users toward Chromium. The author avoids speculating about Apple's motivations and argues that browser diversity remains important.

## Source excerpt

There's been a lot of discussion recently about how "Safari is the new IE" (1, 2, 3, 4, 5). I don't want to rehash the basics of that, but I have seen some interesting rebuttals, most commonly: Safari is actually protecting the web, by resisting adding unnecessary and experimental features that create security/privacy/bloat problems. That is worth further discussion, because it's widespread, and wrong. More specifically, Safari's approach isn't protecting the web from bloat & evil Google influence, because: Most features that Safari hasn't implemented have no hint of security, privacy or performance concerns, and they've been implemented in every other browser already. The largest Safari complaint is unrelated to experimental features from the Chrome team: it's the showstopping bugs in implemented features, made worse by Safari's slow release cycle. Refusing to engage with the contentious API proposals for real use cases doesn't actually protect the web anyway - it just pushes web developers and users into the arms of Chromium. We'll dig into each of these points in more detail in a second, and then we'll talk about what Safari could do instead. There have been other arguments made too, including much speculation about why Safari might be killing the web - is this motivated by protecting Apple's app store profits? I'm going to ignore those suggestions entirely, and stick to concrete problems. Their reasons are their own, outside Apple we can do little more than guess, and the concrete issues can make the point without conjecture. Before we start, I do want to recognize that the Safari/WebKit team are working hard, and I do desperately want them to succeed! Chromium's domination is bad for everybody, and building a popular browser that's focused on privacy & security, as they appear to be trying to do, is a fantastic goal. That does not mean their current approach deserves our blind support. I'm sure the Safari team are working on the issues below already, and I thin