this post was submitted on 16 Aug 2024
505 points (97.7% liked)

Technology

58009 readers
2916 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. 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
[–] TheOctonaut@mander.xyz 23 points 3 weeks ago (1 children)

If I remember correctly, yes. There was a pain in the ass a few years ago when Firefox switched from their own add-on system to one that matched Chrome's, despite Firefox's being more powerful and mature. The goal was to make it easier to port Chromes (arguably) greater variety of add-ons to Firefox.

It was an unpopular decision and it was the start of a downward decline for Firefox. People that had their browser "just the way I like it" found themselves starting fresh essentially, and without some of their favourite add-ons.

[–] paraphrand@lemmy.world -5 points 3 weeks ago (1 children)

Damn. That means they are once again on a divergent path.

[–] sugar_in_your_tea@sh.itjust.works 9 points 3 weeks ago (1 children)

How so? They can support Manifest v2 and v3 simultaneously. It's a bit harder for their old add-on system since that add-on system had more hooks into the browser, but v3 is largely just a restriction, so there won't be much conflict there.

[–] paraphrand@lemmy.world 4 points 3 weeks ago* (last edited 3 weeks ago) (1 children)

Ah, if it’s easy to just maintain both, and v3 is largely backwards compatible then I’m mistaken on how divergent v3 is.

Defanged/declawed v3 is a weird thing to have exist. It’s a bummer that Chrome got to set the standard. And then they took that and restricted things. This isn’t a healthy standard.

[–] sugar_in_your_tea@sh.itjust.works 4 points 3 weeks ago* (last edited 3 weeks ago)

If FF ever drops V3, it'll be because they have extensions to bring parity to V2. There is maintenance overhead, but I doubt it's anywhere close to the old add-on vs V2 differences.