uBlock Origin is available on Safari. Installing it results in a "will slow down your browser" which is apparently just a CYA warning from Apple for any extensions not installed via the App Store.

https://safari-extensions.apple.com/details/?id=com.el1t.uBl...

It's not 'a CYA warning'. The in-process JS extension API is going away.

Safari supports multiple user profiles because it’s running on a Unix operating system that provides full user accounts.

If you’re switching browser because google is breaking ad blocking, it absolutely makes sense to switch to one with a blocking technology that the browser vendor specifically added, rather than grudgingly allowed.

It also makes sense to use a browser where the blockers don’t get access to what you’re actually browsing. What’s the point of blocking trackers if the blocker just tracks what you do?

Unless you want to log out and into another mac account just to change profiles, this really isn't useful.

The utility comes from having multiple sandboxed, separate profiles running at the same time with separate cookie jars, in separate memory spaces. Kind of like docker containers for the browser. Chrome does this magnificently--I have personal, school, and work profiles all running and open at the same time. It's very useful if you have multiple accounts on any services and need access to them simultaneously (i.e. multiple google accounts). Also useful if you don't want the browser in one of the profiles to remember any sites/cookies from another area of your life. I wouldn't want some of sites I visit on my own time to autocomplete at work, but I still want to have it when I go home.

As far as I know it also isn't possible to make any sort of CLI incantation to open the safari binary as a different user (like sudo with specifying a different non-root user) and not have it override whatever is currently running.

https://www.bettercloud.com/monitor/the-academy/how-to-creat...

I seriously did not expect the terrible "macOS is a CERTIFIED(C) UNIX(R)(TM)" argument to be deployed in this manner.

That extension has been dead for over a year.

For it to work on future macOS versions, the developers would need to convert it to a Safari App Extension and cough up $99/year. They’re not interested.

It's not the money. The extensions would have to be ported over to Swift or Objective-C. Complete rewrite of what was JS code previously

I seem to recall an issue on Github where they claimed the cost of an Apple Developer Account was a deterrent, but I may be misremembering.

I don't think you need to pay to develop a Safari App Extension.

You do if you want to sign and publish it.