Probably not. Yeah we have web standards and some idea of how to architect it, but the total set of APIs and HTML/CSS features a browser supports is probably changing faster than the Ladybird team can actively implement it. The API surface is just impossibly large compared to 10 or 15 years ago. Look at all of these: https://developer.mozilla.org/en-US/docs/Web/API
And that doesn't include the updates to Javascript, MathML, SVG, HTTP-based security features, encryption or media support.
- standards are really detailed at this point and a large reason why the three remaining browser engines (chromium, safari, and firefox) largely do exactly the same things.
- There are a lot of open source components. It's not necessary to start from scratch on things like wasm and javascript interpreters for example. There are some nice low level graphics libraries out there as well. And of course things like Rust are now pretty mature and there's a lot of rust code out there that does stuff that a browser would need.
That being said, it's one hell of a hobby project to take on and I don't see much economical value in an independent implementation of something provided by free by three independent browsers already; two of which are open source.
Which begs the question: why?!? Is there qualitative argument here of doing the exact same thing but somehow better?
The main argument for doing it is because it is fun, just as with SerenityOS. Having alternative implementations is never a bad thing for web diversity though.
If anyone threatens Google position, they can literally throw money at the problem, invent some overcomplicated standard, implement it in Blink, and have the competition chase them. It doesn't need to go through W3C either, if it works in Chrome, all web developers will adopt it and any smaller engine will necessarily have to support it or risk losing whatever little market share they have left.
Having control of the internet now is of greater strategic importance than it was 20-30 years ago when Microsoft was king of the hill.
It is conceptually despicable, especially for devs, but it prevents Google from completely running the show.
Now the European Union is coming after Apple without trying to rein in Google's influence... This seems short-sighted.
I think you have a fundamental misunderstanding of the goals of the EU in this matter. The objective is not to keep both companies on even keel, but it is merely about enforcing existing anti-monopoly laws. If this results in Google gaining a de-facto browser monopoly then those same laws can be used to break up that monopoly when we get to it.
What would be the alternative in your opinion? Allow Apple to break the monopoly laws in hope that they will be able to rein in the growth of the Google browser? What good is a law if it will not be enforced?
Force Apple to allow alternative rendering engines, but only the ones with <50% market share. This would promote diversity in rendering engines without giving what is already by far the most dominant rendering engine the opportunity to get more of a stranglehold over the market.
People already mistake Blink-only APIs like Web USB, Web Bluetooth, Web MIDI, etc. for web standards. The market is already dangerously close to where it was 20 years ago, where a vast number of web developers treat the most popular rendering engine as if it’s synonymous with the web. Handing more opportunities for market share to Blink is playing with fire.
You want Apple to allow Gecko or Ladybird? Sounds great! But the monopoly that threatens the web at the moment is Blink.
That means no more “download Chrome” prompts on Google search and YouTube, no pestering people to install Chrome when tapping links in Google iOS apps, no bundling of Chrome in installers of unrelated software (very common on Windows), etc.
Some sort of rule against favoring one’s own browser in web apps (as has happened with GSuite and YouTube on multiple occasions) would also be nice but unfortunately strikes me as unlikely.
That's just playing sides.
It would be nice if there were more alternatives, but I can't really expect anyone to spend the resources necessary. I don't think crippling chrome for some kind of sense of "fairness" is a productive solution.
I'd like to take issue with this statement...its spyware, and its atrocious to modify. You can't slim down a chrome browser, and it can force you to do whatever it wants to...
It's actually really, really bad...
It's never ever that simple in politics, and this is about a new law (Digital Markets Act). Ask yourself:
- How were all the terms in the Digital Markets Act determined?
- Which players or initiatives were able to scoot by unnoticed (e.g. Chrome's grip on web standards)?
- What is the interpretation of what constitutes a gatekeeper? (note: its actually 'gatekeeper' not monopoly we're talking about).
- Who will decide whether Apple's changes are in compliance?
It can be true that their aims are generally to have more fairness in the market, but there's always going to be other factors at play in this kind of legislation. Note that the DMA was written in a way that allowed Europe-based Spotify and Booking.com to avoid being labeled gatekeepers.
Booking.com is registered in the US...
Spotify is definitely no money maker. That said, its market share alone would/should put it in the crosshairs of gatekeeping laws.
At the very least, if the EU really wants to limit the tech giants' grip on the web, it needs to fund independent open source web engine development handsomely; their pockets are more than deep enough and projects like ladybird and servo can use the extra resources.
You're misunderstanding the goals of the EU. The EU only cares about limiting their grip as a result of their main goal. The main goal of the EU is to protect the rights of their citizens, which they do by enforcing existing anti-monopoly laws.
The EU has in principle no problem with a company gaining giant market share by providing a successful service or product. There would be no problem if Google or Apple would gain 99% market share by everybody voluntarily choosing their product. But it is a problem if they then use that marketshare to make it harder for competitors to compete.
I.e.: you're wrong to say that they're trying to minimise the 'grip' they have. They are merely trying to prevent companies abusing that grip.
That being said; I'm pretty sure that the EU does actually fund a lot of open source development
> In addition, apps that use alternative browser engines — other than Apple’s WebKit — may negatively affect the user experience, including impacts to system performance and battery life.
https://www.apple.com/newsroom/2024/01/apple-announces-chang...
The performance improvements are nice, but trying to make a Firefox another Chromium skin irks me. Plus I still miss the official compact mode.
That's the problem. They should go after Google too. Honestly all of these megacorporations should be broken up.
This is why we, tech nerds who understand the problem, must resist monopolies: object to using such APIs. Chrome wouldn't be in quite this position if, instead of embracing the monopolist, more techies had warned their non-techy friends and family away from it, like they did with IE.
They didn't listen or care.
Elsewhere in this comment section someone literally said they use Chrome because Reddit does not work in Firefox, which is utter nonsense.
Becoming part of it isn't hard either, if you test software either as a SW engineer on a team or as a full time tester it might actually save you some time :
- If you use Mac, test in Safari first. On any other platform, install Firefox (or the Debian version, or Librewolf) and use it as the first tool to test applications.
- If it doesn't work (and the customer hasn't very explicitly said they absolutely only care about Chrome or IE^CEdge) report it as a bug.
I mean, seriously, who would have accepted a feature that only worked in IE 6?
---------
OK, some people might say: but IE 6 was an old and outdated browser, you cannot compare IE 6, or any version of IE for that matter to Chrome.
Or one might say: Chrome has already won, your idealism is appreciated, but you are too late.
Well, here is the thing: IE was at one point in almost the exact same postition as Chrome is now:
- biggest browser by far
- endorsed (or even enforced) by IT
- lots of features only worked in IE. (I remember one particular customer who seemed to be obsessed with security to the point were we had to keep a VM with Windows XP and IE 8 around with both Active X and Java Applets enabled to sign into them. This was around 2014..! Yes, if you find this notion of security absolutely ridiculous then we agree.)
---------
OK, one key difference:
Back in 2006 when I started fighting IE we had Mozilla on our side. Firefox was innovating like crazy. We had extensions that let us embed IE in a tab to render certain web sites. We could automatically archive a full website for offline access (full rewrite of links so they worked on our copy was included). Full developer tools that everyone knows from every browser these days started out as just an extension to Firefox, named Firebug IIRC.
Today, while I understand that the extension API had to be reigned in before a disaster happened, it went way to far and today we cannot even get a function in the API to programmatically remove the top tab bar when we add a tab bar on the side. And not only that, but if someone asks about that particular issue, someone will come and hush and hide the comment.
So godspeed to Ladybird devs and Orion devs, Librewolf devs and actually even Safari devs and everyone else who challenges the current monopoly!
Doesn't work since the corporation can just fire you and replace you with someone who has no such objections.
How is Instagram dependent on whatever Google decides? How is Facebook, TikTok and Snapchat? How are streaming platforms dependent on Chrome? Big businesses with a ton of users easily launch their own apps to sidestep Chrome. And if Chrome makes fundamental breaks of HTML and CSS, then most of the internet is going to be broken in Chrome.
If your bank website stops working in Chrome, they're not going to change their website. They're going to ask you to install another browser.
People can change browser more easily than changing banks. They can even have multiple different browsers on their machine, and one for only doing banking.
It's almost as if backwards-compatibility is seen as something to be avoided in certain web dev communities. Lots of "drop support" and "moving forward", zero consideration for simplicity and interoperability.
A decade back, maybe... but decades ago the number of things you had to support was just so much smaller even if you only looked at HTML! Consider https://www.ietf.org/rfc/rfc1866.txt vs https://html.spec.whatwg.org/multipage/
Writing a web browser was hard in the old days for a lot of reasons, but trying to write a full-featured one today is a huge undertaking and we're still adding a bunch of new features all the time and expecting browsers to support them
I thought, oh, that's not so bad. Then I realized what I was looking at was a 10 page index.
Thanks jug! I'm super proud of all the folks who have worked on it with me :^)
> However, the thought has also crossed my mind if we're finally seeing fruits of browsers being better standardized on "95%"+ of the popular features -- and if writing a browser today is in fact easier than both writing AND maintaining a browser a decade back. While the web is of course still evolving, it feels more "settled in" than 10-15 years ago
This is definitely true! I've worked on browsers on and off since 2006, and it's a very different landscape today. Specs are better than ever and there's a treasure trove of tests available.
1. https://www.webkit.org/blog/14633/get-ready-for-interop-2024...
The idea of being able to ship an XML template with basic logic like for loops alongside the actual XML data source is really unique today. If people cared to use XML at all, that really does cover quite a few use cases that we current reach for JSON + client JS today.
However, the thought has also crossed my mind if we're finally seeing fruits of browsers being better standardized on "95%"+ of the popular features -- and if writing a browser today is in fact easier than both writing AND maintaining a browser a decade back. While the web is of course still evolving, it feels more "settled in" than 10-15 years ago.
There's also the factor that past developers didn't have the more complete roadmap set when they initially planned browser design, but now we have huge amounts of web standards already there AND also know how popular they got over time i.e. what to prioritize to support a modern web. One might superficially think there's simply more of everything, but I also think ideas that can be discarded. Just imagine that Internet Explorer had XSLT support, and FTP was common once upon a time!
It would be interesting to hear more about their own thoughts on these topics!
Edit: My bad; XSLT is still commonly supported and by all major browsers but a rarely used feature and stuck in limbo in XSLT 1.0. So it's probably among those things that can be safely omitted for quite some time.