They are doing it though; it's "real." Perhaps you are setting goals for them that they are not themselves setting?
> can't compete
You actually can read about their goals on the linked page, though. They are not attempting to "compete" with Chromium.
> iphone
So don't use iPhone, and use a phone that allows you to use the browser engine you want to!
It's obviously the grandparent meant it as not a toy implementation. As in, non computer literate people can use it without complaining about broken sites.
The first 80% will take 10% of time. Now last 20% will take 90% of the time.
There are lots of tiny quasi browsers lying around.
Apparently they can't but they still do. Typing this from a mozilla browser.
> realistic
Having looked at the project and followed a few serenityos updates videos and if there is one word I would do to describe Andreas Kling and his contributors is that they are realistic about what they do and do not.
Same, but I doubt I'll continue to do so in far future, unless something major changes. Mozilla seems to be inching closer and closer to just another Chromium.
Like Google being forced to remove Chrome integration.
Not sure I understand this. I mean Chrome drives the feature set and performance, but it's not like Mozilla's switching to Blink/v8 AFAIK. Competition is good. Even the proliferation of WebKit/Blink browsers is fine to me.
I run into the occasional site that does the block-by-user agent of ye olde IE days and an odd niche commercial product used by my company that only works in Chrome or Safari. And honestly, I hit more of the latter that only work in IE and I have to RDP to an old windows server host to use them.
I like the Firefox UI better, and it doesn't get as sluggish as fill-in-your-chrome on my Mac. Now, that's "feel" and not measurable. Safari's a lot snappier, but too sparse for me. To me, browsers and OSes are like shoes. Pick what's comfortable to you. There's not a "right" answer.
Addressing the thread more than you: This project never states it's trying to slay the giant. The whole argument is weird. I'll play with it once I can without compiling (I'm lazier than I used to be). It'll be fun. Probably not a daily driver, but interesting.
And who knows? KHTML was a broken (and oft neglected) toy and now dominates with world via Blink/WebKit. We may all bemoan Ladybird in 20 years.
For now. If they are willing to fire their Servo team, MDN on a whim. Why not fire your engine team and outsource it to Chromium/Blink?
> Pick what's comfortable to you.
That's the issue. I like Firefox, but I have doubts that they'll soon replace their shoes with a model that is two sizes smaller for me.
> And who knows? KHTML was a broken (and oft neglected) toy and now dominates with world via Blink/WebKit. We may all bemoan Ladybird in 20 years.
Only after two big corps (Apple and Google) injected huge amount of cash and developer man hours on it.
Google has been caught sabotaging browser based on user agent.
In addition to its strong marketing machine.
I suggest reading https://justforfunnoreally.dev/ .
- a developer who uses firefox 99% of the time
There is no winning going down this road for Mozilla other than maybe going the firefox phone route, and we all saw how that went.
I'm afraid there is no route for sustainability for Mozilla at this point.
maybe if mozilla tried to compete, instead of all the irellevant activities they waste their energy on
you are lost.
And the elephant in the room, regardless of adoption it will never be on iphone.