Mozilla is trying to innovate and bring new features to Firefox, but the browser continues to lose users. Despite these concerning market trends, the company is actively...
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.
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.
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.
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.
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.
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.
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.