| ▲ | argsnd 7 hours ago | |
There’s quite a difference between a one time $5 fee and an annual $99 fee for the economics of publishing a free browser extension. Given almost 100% compatibility with the same Web Extension APIs that Chrome uses, I think you’d expect near-parity in extension availability between Chrome and Safari if that barrier didn’t exist. | ||
| ▲ | lapcat 7 hours ago | parent [-] | |
> There’s quite a difference between a one time $5 fee and an annual $99 fee for the economics of publishing a free browser extension. Yes? I didn't deny that. I said your initial comment didn't mention cost. > Given almost 100% compatibility with the same Web Extension APIs that Chrome uses, I think you’d expect near-parity in extension availability between Chrome and Safari if that barrier didn’t exist. It feels like you ignored the points I made in my last comment. Why would you expect near parity in extension availability when you can't even develop Safari extensions on Windows and Linux computers? | ||