Ironically, we already had that - Microsoft’s first version of Edge was using their own engine. On release, it had the highest W3C compatibility score.
Google started shitting on it (including things like serving clear HTML version of Gmail because “the browser is outdated” if it detected the Edge user agent) and massive self-delusion campaigns of “Edge is just Internet Explorer” eventually killed the thing and forced MS to switch to Chromium.
I have Ladybird installed and I check it out every now and then, but I honestly doubt that a bunch of random developers will succeed where Microsoft failed. Unless Cloudflare somehow chips in and forces Google’s hand into compatibility, but I don’t know if even they are big enough to do that.
Personally, I think if the engine was closed source, then we didn’t in fact “had that”. Maybe Microsoft had it, not us.
What makes things like chromium, firefox and webkit actual ecosystems is that they at least have an open source basis. Edge isn’t an ecosystem, it’s a black box. We don’t even know whether it’s true or not that it was its own thing or just they sneakily used bits and pieces of chromium from the start anyway.
User Agent checks is the easiest thing to overcome. Had edge’s engine been open source we would have had spins of it resolving the issue within hours. There are many examples of “random developers” succeeding where big companies tied by business strategies (I bet they had business reasons to keep a distinctive user agent) didn’t, to the point that the web runs on servers using FOSS software.
Yes, I understand that. But in my view, Microsoft is the one that might have had “a non Google-reliant engine” (if it’s true that they didn’t rely on Google code).
They just let us use it under their conditions, for the limited time they decided to make it available to us… but it was never “ours”. We were just contractually allowed to use it, but we didn’t really “have” it.
Yes, the matter of fact is that the reason why that choice was taken away is because everyone except MS was forbidden from “having” that engine. It might have still been alive today in some form had it not been an exclusive MS-owned thing.
I imagine the reason that Cloudflare is doing this now is that Google just got off with no punishment from their antitrust loss.
Anybody who competes with Google now has to worry that they’ll do to them what they did to Microsoft. And, with Trump’s DOJ, the government will probably just ignore it if Sundar Pichai shows up with a shiny bauble for Trump. So, I’d imagine that Microsoft, Cloudflare, Amazon (AWS, Twitch), and Meta, among others, might all decide to fund an alternative browser.
Microsoft - in theory - had the finances to push their browser to peoples homes. Be it by baking it in to Windows, by ad campaigns, etc., etc. And they still lost to Google’s control over the Web.
Ladybird, by comparison, is an obscure no-name product, being made by a controversial figure, with (relatively to MS) zero ability to market itself to the wider audience. All Google has to do is make their products completely inoperable under Ladybird and, other than some extremely committed power-users who want to “de-google” their lives, nobody will use it.
Ladybird is not threatened to be killed by whatever anybody but the developers do.
It absolutely is. If Google forces incompatibility on it (like it did with Edge) ordinary users won’t switch. Because the majority of ordinary users are still deep in the ecosystem.
All it takes is for Google to block high quality streaming on YouTube and the browser will never go outside of 2-3% market share.
But we’re discussing the potential future of the browser, not its current state. Right now it can barely render a modern page without crashing (but not always).
What’s not bad? Ladybird sitting at floor-leves of market share?
If we want to threaten the status quo in any way, it absolutely is. Firefox has 2.26% and - in terms of defining standards or forcing changes upon Chromium - it’s 100% irrelevant.
Ironically, we already had that - Microsoft’s first version of Edge was using their own engine. On release, it had the highest W3C compatibility score.
Google started shitting on it (including things like serving clear HTML version of Gmail because “the browser is outdated” if it detected the Edge user agent) and massive self-delusion campaigns of “Edge is just Internet Explorer” eventually killed the thing and forced MS to switch to Chromium.
I have Ladybird installed and I check it out every now and then, but I honestly doubt that a bunch of random developers will succeed where Microsoft failed. Unless Cloudflare somehow chips in and forces Google’s hand into compatibility, but I don’t know if even they are big enough to do that.
Personally, I think if the engine was closed source, then we didn’t in fact “had that”. Maybe Microsoft had it, not us.
What makes things like chromium, firefox and webkit actual ecosystems is that they at least have an open source basis. Edge isn’t an ecosystem, it’s a black box. We don’t even know whether it’s true or not that it was its own thing or just they sneakily used bits and pieces of chromium from the start anyway.
User Agent checks is the easiest thing to overcome. Had edge’s engine been open source we would have had spins of it resolving the issue within hours. There are many examples of “random developers” succeeding where big companies tied by business strategies (I bet they had business reasons to keep a distinctive user agent) didn’t, to the point that the web runs on servers using FOSS software.
Well, yeah, in that aspect, you’re correct. I meant that as a “we had a non Google-reliant engine”.
Yes, I understand that. But in my view, Microsoft is the one that might have had “a non Google-reliant engine” (if it’s true that they didn’t rely on Google code).
They just let us use it under their conditions, for the limited time they decided to make it available to us… but it was never “ours”. We were just contractually allowed to use it, but we didn’t really “have” it.
Semantics. I agree with you in principle, but the matter of fact is that we ended up with effectively zero choice over the browser engine.
Yes, the matter of fact is that the reason why that choice was taken away is because everyone except MS was forbidden from “having” that engine. It might have still been alive today in some form had it not been an exclusive MS-owned thing.
I imagine the reason that Cloudflare is doing this now is that Google just got off with no punishment from their antitrust loss.
Anybody who competes with Google now has to worry that they’ll do to them what they did to Microsoft. And, with Trump’s DOJ, the government will probably just ignore it if Sundar Pichai shows up with a shiny bauble for Trump. So, I’d imagine that Microsoft, Cloudflare, Amazon (AWS, Twitch), and Meta, among others, might all decide to fund an alternative browser.
Ladybird doesn’t have to be profitable and the org cannot be bought.
Not what I meant.
Microsoft - in theory - had the finances to push their browser to peoples homes. Be it by baking it in to Windows, by ad campaigns, etc., etc. And they still lost to Google’s control over the Web.
Ladybird, by comparison, is an obscure no-name product, being made by a controversial figure, with (relatively to MS) zero ability to market itself to the wider audience. All Google has to do is make their products completely inoperable under Ladybird and, other than some extremely committed power-users who want to “de-google” their lives, nobody will use it.
You are right, but as you noticed, we don’t argue the same thing.
Ladybird is not threatened to be killed by whatever anybody but the developers do.
It absolutely is. If Google forces incompatibility on it (like it did with Edge) ordinary users won’t switch. Because the majority of ordinary users are still deep in the ecosystem.
All it takes is for Google to block high quality streaming on YouTube and the browser will never go outside of 2-3% market share.
I think not being a default browser means that, for now, it’s not for ordinary users anyway.
But we’re discussing the potential future of the browser, not its current state. Right now it can barely render a modern page without crashing (but not always).
That’s not bad.
What’s not bad? Ladybird sitting at floor-leves of market share?
If we want to threaten the status quo in any way, it absolutely is. Firefox has 2.26% and - in terms of defining standards or forcing changes upon Chromium - it’s 100% irrelevant.
To threaten the status quo it’s bad but to have fun programming a browser it’s not bad.