I likely won’t touch it anyway, but it is fully open source, so it can be forked easily. With the transition to Swift I suspect there would be plenty of devs who could take things forward if they wanted to.
If you look at history, Google did the opposite with Chrome, they forked an open source browser and turned it into the world’s most used.
I guess we’ll see.
Thats google though, with the added ability to put it direct into an extremely common OS (Android). With ladybird, you’ve got an apparent neocon and 3 years currently planned for a GA release (2028). Its future is already pretty uncertain regardless of sponsorship.
and what can they do against the manifest v3 migration? they cannot afford to keep maintaining the code for mv2 addons. it is an important topic for efficient content blocking.
its funny you bring up edge as an alternative. brave too has opt-out telemetry and other shenanigans.
I was answering forking and how realistic it is. You’re changing the conversation into specifics around chrome.
As I mentioned, this would be (not is, because its not even at a GA state) drastically simpler to fork, and there are many forks of a substantially more complicated browser already.
I was answering forking and how realistic it is. You’re changing the conversation into specifics around chrome.
I’m not changing anything. they are powerless. if google decides to change chrome for the worse in a more significant way than UI design, they cannot avoid accepting that change.
For now
So when they do just fork it?
I likely won’t touch it anyway, but it is fully open source, so it can be forked easily. With the transition to Swift I suspect there would be plenty of devs who could take things forward if they wanted to.
If you look at history, Google did the opposite with Chrome, they forked an open source browser and turned it into the world’s most used.
I guess we’ll see.
Thats google though, with the added ability to put it direct into an extremely common OS (Android). With ladybird, you’ve got an apparent neocon and 3 years currently planned for a GA release (2028). Its future is already pretty uncertain regardless of sponsorship.
say the same for chrome, and think again if you mean it seriously.
Iridium, cromite, edge, brave, thorium, vivaldi, pale moon…
And this is a drastically simpler browser that would be in swift 6.
and what can they do against the manifest v3 migration? they cannot afford to keep maintaining the code for mv2 addons. it is an important topic for efficient content blocking.
its funny you bring up edge as an alternative. brave too has opt-out telemetry and other shenanigans.
I was answering forking and how realistic it is. You’re changing the conversation into specifics around chrome.
As I mentioned, this would be (not is, because its not even at a GA state) drastically simpler to fork, and there are many forks of a substantially more complicated browser already.
I’m not changing anything. they are powerless. if google decides to change chrome for the worse in a more significant way than UI design, they cannot avoid accepting that change.
Sure thing bud.
Now back to the actual topic…