this post was submitted on 18 Jun 2026
231 points (93.6% liked)

Technology

85606 readers
3788 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 news or articles.
  3. Be excellent to each other!
  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, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots


founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] brucethemoose@lemmy.world 0 points 2 days ago* (last edited 2 days ago) (1 children)

The brand, development power, and bits from the Firefox codebase they could re-use.

More importantly, Firefox’s devs get to work on something that already has leverage in an ecosystem, eg WebKit for Apple or Ladybird for Linux.

[–] CameronDev@programming.dev 4 points 2 days ago (1 children)

Developers can just be hired directly, and the Firefox codebase is open source.

Only brand requires partnering with mozilla, and what does the other partner gain from the Mozilla brand? They don't even have much brand recognition anymore anyway.

[–] brucethemoose@lemmy.world 2 points 2 days ago* (last edited 2 days ago) (1 children)

I ninja edited, but basically I just don’t see Firefox surviving without “ecosystem leverage” like WebKit, which is permanently embedded in the Apple ecosystem.

Or even Ladybird, which I imagine will be a permanent fixture on Linux systems.

So… however they organize it, Mozilla should take their browser dev experience there. But maybe they could keep Firefox the brand alive, and automatically shift users to whatever the new rendering engine will be.


Alternatively I guess Firefox could stay Mozilla and just adopt WebKit or Ladybird’s engine. “Merge” development efforts across different teams, so to speak, but keep the browser frontend separate.

[–] CameronDev@programming.dev 6 points 2 days ago

Its a bit early to make the call that Ladybird will be successful. They have made a lot of noise sure, but they are a small team, tackling a huge project, and they have just had 2 language changes in the last few months.

The deck is well and truely stacked against them. Maybe they pull it off, maybe not, but its very early to make the call IMO.

Servo is looking surprisingly good, but still has major rendering issues. At least it looks like a browser now.