Safari 14 added WebExtensions support, so where are the extensions?

I wonder if the bigger hurdle here is that you have to spend money to get into the developer program (unless this is waived for these kinds of apps, I couldn’t tell when trying to dig up an answer)

I don’t know that effectively slapping an app shell around an extension is a big hurdle, but no other web extension store charges for entry, so that very well could be the real barrier here.

People who use Safari aren't the same kind of people that use browser extensions.

100% Untrue. I use many extensions in Safari just like I use to in Chrome, my needs for customization are the same regardless the browser I use, but like many choose Safari for his performance, privacy ui, among other benefits. Find it very frustrating that many of the big products don't have Safari extensions. Often when I email there tech support they give a reason why, and then I try to explain there are referring to how extensions worked before, rather than how Safari extensions work now. So imagine a lot of companies don't know about the changes, or think they don't need to because they don't have enough people asking for them, but people probably did ask for them but were told it was not possible before, so they stopped asking.

In addition to the money argument raised in another comment, the Apple development experience is a major annoyance when all you need is a couple lines of JS.

I have an extension idea; it's literally a single line of JS. However, to get it into Safari, I need to create a (useless, and empty) Mac app with a specific configuration in Xcode that'll allow it to appear in the "extensions" list in Safari. Then I need to deal with all the signing & App Store distribution stuff if I actually want to distribute it.

The money isn't even an issue (I have a developer license for other reasons - creating actual apps), it's just the annoyance and insane barrier of entry when the majority of extensions don't need anything but JS.

There's also the issue of how Safari discovers extensions and what actually causes your extension to appear in its list. Is it opening the associated "app"? Not always as I've had trouble with that before - the app is compiled, it's open, but the extension is nowhere to be seen in Safari's preferences. It mysteriously self-resolved after some more trial and error. Updating the extension's JS while developing is also unclear. Does it happen upon app recompile? App relaunch? Who knows - I gave up before even reaching this stage - this whole process is bullshit.

The whole idea that browser extensions are "apps" is stupid and annoying. They should be separate, and while apps install on your OS, browser extensions install in your browser. They should have their own file format (openable directly by Safari, with optional code signature checks) and their own Store (a website within Safari). At least that would solve the problem above - you open an extension file in your browser and it installs in your browser - no ambiguity there. To update you open a new file (which overwrites the previous one based on a potentially signed Bundle ID or similar) and it updates.

The worst is that they had all of the above already and then decided to shit all over it about 2 years ago (in addition to removing much-needed APIs that allowed uBlock Origin to work and replaced it with something way less powerful).

That is definitely the reason I haven't tried to develop anything for the Apple ecosystem even though I've used it for more than a decade. $100 a year is wasted money for hobby projects which may not even be published in an app store.