ungoogled-chromium-macos VS ladybird

Ungoogled chrome for mac did not have a single release between Feb 2021 and March 2023. Unless I am missing something.

I readily admit that cooking the mozconfig is some holy hell, but they do have real-world examples in the repo; did you experience problems at that stage, or it literally wouldn't compile?

And while I haven't tried Ungoogled-Chromium, for unrelated reasons I helped an OSS project build their Brave-derivative in a container, so that may interest you: https://github.com/imperviousinc/beacon/blob/main/Dockerfile The only reason it's not already GitHub Actions for them is the chromium_src is 38GB and GHA cache is capped at 10G, but while digging up the link to that Dockerfile, I was reminded that there is a GHA for the macos build: https://github.com/ungoogled-software/ungoogled-chromium-mac...

While I haven't personally tried it, and they are incredibly behind the upstream Chromium versions, the ungoogled chromium for macOS repo has a bunch of GitHub Actions workflows and scripts that may also be interesting

My only issue with it is, that you can only get it from certain Github sites, which you have to trust, as the original project only releases the source code, that you are probaly supposed to compile yourself, which I can't and don't do. This also leads to lagging a bit behind the regular updates that other browsers receive, as you have to wait for someone to package and release it. The Mac version of UC can be downloaded here.

Just use unGoogled Chromium https://github.com/ungoogled-software/ungoogled-chromium-macos

A browser is not a web app, it doesn't have a strict separation of "frontend" and "backend" in the same sense that a web app would have; the lines are drawn quite differently. The rendering engine is never "just" the rendering engine; you can't abstract or swap it without tremendous effort.

If you'd like to learn more about how a web browser project would organize its internal architecture, but are discouraged by the complexity of Chromium, Firefox, etc. I'd recommend source diving Ladybird (https://github.com/SerenityOS/ladybird), NetSurf (https://www.netsurf-browser.org/), or Dillo (https://www.dillo.org/).

I'd love to see a stable version of a brand new web browser, not based on Blink or Gecko, such as Ladybird or Flow Browser. Competition is a good thing.

note, native Windows is not currently supported:

https://github.com/SerenityOS/ladybird/issues/113

Google is dominating, pushing through Android and via Googles-Webservices and Microsoft is using it now. A reason to worry because developing new web-engine requires an big effort. For instance Microsoft only allows usage of Microsoft Teams Web with a webbrowser based upon Blink. So were back in 2002?

WebKit features also WebKit2Gtk (Epiphany) and Qt5-webkit (Otter) with native integration. They use the native toolkits, which is an advantage! Interaction with the open-source community around WebKit seems rather good and the engine is integrated by others. Gecko seem not to be integrated by others, but by forks only? You remember when Chrome was considered slick and fast? Originally Google used the native toolkit on every platform but know they use an own solution on every platform, like Firefox.

Maybe there is a new kid on the block:

https://github.com/SerenityOS/ladybird

Funny you should ask: https://github.com/SerenityOS/ladybird

I've not heard of Ladybird before. True, it's a free and open browser engine and a very interesting project!