Comment by rice7th
8 months ago
And so? Yes people (and companies) would fork your code, but the most realistic scenario would be that the original ladybird would still be the most relevant browser of it's family, just like firefox, so the problem kinda resolves by itself
Then why KDE's Konqueror is not the most prominent browser of the KHTML family, but Safari is?
Because apple themselves forked it. Only a handful of companies have the power to basically change the web browser market, and apple sure was one. Nowadays every company copies from chrome, so why would anyone bother forking ladybird?
Doesn't this contradict with what you said? According to your previous comment, even if Apple has forked KHTML, it shouldn't harm Konqueror, and it shall prevail as the most popular of its family.
However, Konqueror/KHTML is now dead and we only have a closed source Safari.
I can't fathom your comments back to back.
1 reply →
Imagine if ladybird gets used regularly by ~1000 nerds, which is its current audience, then gets forked by microsoft and the current ME gets replaced by ladybird. Even if ladybird got over 9000 users, there's no competing with megacorps.
Also, its* not it's
Well maybe they're ok with that? They want browser diversity. Getting Microsoft to use a new engine is better for diversity than if they just used chromium like now.
Getting Microsoft to use a new engine and contribute back to the original repository is better for diversity, but forking and running away with it is certainly not.
4 replies →
Sorry for my grammatical mistake, English is not my first language.
That said, my point here was that realistically no company is going to fork ladybird since there's already chromium, plus even if ladybird was somehow forked by let's say microsoft and got popular, I don't think it would be detrimental to ladybird itself, if not even beneficial, since it would attract more users and, to a lesser extent, more contributors.