this post was submitted on 29 Nov 2023
866 points (99.1% liked)
Technology
58201 readers
3617 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
That’s not the reason; Safari and the like still support the WebExtensions API (the same the Firefox uses). They just require extensions to be signed, .app’d, distribute through App Store etc. and maybe only go to Safari which is a lot.
I read this over and over and it makes no sense to me. Even if you were right, do we really think that FF extension devs are going to make and maintain a completely separate codebase for a iOS-only FF version of each extension? I highly, highly, doubt anyone would do that.
Then on top of it, yeah, maybe you'd have to kiss Apple's ass to ever get it installed on a user's device. In any case, Fuck apple with a cactus.
It’s the same codebase. Safari can use extensions written for Firefox as long as you compile it into Apple format.
Bizarre. All these years, every time I have tried to use a safari extension, even very popular ones like 1password, I've had issues. So I feel like it's historically not been as simple as this... Maybe it is now, but all the web devs I know HATE safari. Myself included.
I mean, you've still got the entire signing BS so there is a very valid reason to hate.