Safari adopts the Chrome/Firefox extension model
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:<p>- Current Safari users can get the goodness of Chrome extensions, specifically the ones focused on privacy such as NoScript and uBlock.<p>- Switchers from Chrome can feel familiar with Safari if their Chrome extensions are available to them in the new browser.<p>- New macOS users don’t need to select a browser based on whether extensions are available for it or not.<p>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.<p>Net-net, kudos to the team for getting past their “Not Invented Here” instincts and going with the market flow.