<story><title>Safari adopts the Chrome/Firefox extension model</title><url>https://developer.apple.com/news/?id=kuswih5l</url></story><parent_chain><item><author>jhatax</author><text>I think this was only a matter of time. The Chrome extension model has become the de facto standard, has a large existing extension ecosystem and huge user base, and other browsers have adopted this model. While sticking to their own extension model would ensure that they remained in control, this is the right thing for users, both current and possible switchers. Here’s why:&lt;p&gt;- Current Safari users can get the goodness of Chrome extensions, specifically the ones focused on privacy such as NoScript and uBlock.&lt;p&gt;- Switchers from Chrome can feel familiar with Safari if their Chrome extensions are available to them in the new browser.&lt;p&gt;- New macOS users don’t need to select a browser based on whether extensions are available for it or not.&lt;p&gt;With extension availability out of the way, the discussion on macOS browsers is going to come back to UX, speed, and battery usage. UX is a personal choice. Based on my experience, Safari is the fastest and least battery hungry browser on macOS. Syncing using iCloud Just Works (TM) for my devices and account. YMMV.&lt;p&gt;Net-net, kudos to the team for getting past their “Not Invented Here” instincts and going with the market flow.</text></item></parent_chain><comment><author>bad_user</author><text>Adopting the extension model doesn&amp;#x27;t mean that the capabilities available to extension developers are the same.&lt;p&gt;You can take a look at Firefox, which has extensions that in Chrome are not currently possible. Or extension features that aren&amp;#x27;t possible, like the ability to block first-party analytics in uBlock Origin, as a small example.&lt;p&gt;I am, however, glad that all of them are adopting more or less the same APIs, because extension developers can now target all 3 major browsers with ease.&lt;p&gt;&amp;gt; &lt;i&gt;the discussion on macOS browsers is going to come back to UX, speed, and battery usage&lt;/i&gt;&lt;p&gt;The biggest, most relevant component of a browser has always been the browser engine, because it dictates available features, and yes, speed and battery usage.&lt;p&gt;People keep talking about the UI as being an important differentiator. But I don&amp;#x27;t believe that&amp;#x27;s true, because the UI of all major browsers is decent. Of course, power users can cling on to features, like the Tree Style Tabs in Firefox, but for the most part, I don&amp;#x27;t think it&amp;#x27;s the UI that makes most people switch browsers.</text></comment>
<story><title>Safari adopts the Chrome/Firefox extension model</title><url>https://developer.apple.com/news/?id=kuswih5l</url></story><parent_chain><item><author>jhatax</author><text>I think this was only a matter of time. The Chrome extension model has become the de facto standard, has a large existing extension ecosystem and huge user base, and other browsers have adopted this model. While sticking to their own extension model would ensure that they remained in control, this is the right thing for users, both current and possible switchers. Here’s why:&lt;p&gt;- Current Safari users can get the goodness of Chrome extensions, specifically the ones focused on privacy such as NoScript and uBlock.&lt;p&gt;- Switchers from Chrome can feel familiar with Safari if their Chrome extensions are available to them in the new browser.&lt;p&gt;- New macOS users don’t need to select a browser based on whether extensions are available for it or not.&lt;p&gt;With extension availability out of the way, the discussion on macOS browsers is going to come back to UX, speed, and battery usage. UX is a personal choice. Based on my experience, Safari is the fastest and least battery hungry browser on macOS. Syncing using iCloud Just Works (TM) for my devices and account. YMMV.&lt;p&gt;Net-net, kudos to the team for getting past their “Not Invented Here” instincts and going with the market flow.</text></item></parent_chain><comment><author>_qulr</author><text>NoScript and uBlock Origin will not be happening for Safari. The API is missing and won&amp;#x27;t be implemented. Safari does not have the same full API as Chrome or Firefox. Instead, Safari relies on a more limited, Apple-specific content blocking API.</text></comment>