Safari isn't protecting the web, it's killing it

Click for: original source

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. By Tim Perry.

The article makes plenty of good points summarised under:

  • Safari is killing the web by omitting easy safe features
  • Safari is killing the web through show-stopping bugs
  • Safari is killing the web by ignoring proposed new APIs

The health of the browser ecosystem affects everybody. There are two clear parallels with the past here:

  • The slow death of IE: by offering web developers fewer bugs, better tools and more features while IE stagnated, Firefox built enough developer goodwill to dramatically expand its marketshare against the odds, forcing IE (later Edge) to follow its lead.
  • WebExtensions: despite every browser previously offering their own add-on APIs, Chrome effectively dominated developer mindshare, provided more powerful & easier to use extension APIs that became far more popular, and both Firefox & Safari have eventually killed their own APIs and accepted Chrome’s, unintentionally allowing Google to unilaterally set the web extension standard.

For more follow the link to the full article. Well worth your time!

[Read More]

Tags browsers cloud javascript infosec