fabrice_d

But some parts are far from being trivial engineering and are not part of any specs. Just consider the security infrastructure (multiprocess, sandboxing etc.) and how that impacts the overall design of the engine itself.

Sure, see https://drewdevault.com/weird-guys/#:~:text=2026-,Andreas%20... and check the references to make your own opinion.

Being part of and funded by fascists is not exactly enticing.

All models come with some bias. Given Meta's track record, I would not touch anything from them with a 10 feet pole.

If you can, try again (don't forget to start with `./mach bootstrap` to install dependencies) and open an issue if the build fails. SpiderMonkey is shipped pre-compiled for most architectures, so it's not a big hurdle in terms of build time.

A pure AOSP distribution is now lacking a lot of basic apps. Distributions like LineageOS or GrapheneOS fill the gap with their own, but pure AOSP is totally unusable.

You can switch to the AppView from https://mu.social/ and you'll get editing working.

> You can’t even accurately calculate things like post likes.

And maybe that's a good thing.

I don't believe this is a good solution: users will obviously click on that add-on install dialog box without being better informed and protected against malicious / buggy / attacker controlled web sites.

Hopefully they will move to a better solution that offers some integrity guarantees instead, like https://rwc26.waict.dev/ that they have an early implementation of in nightly builds.

It has build.rs that will run as soon as you compile the dependency. That's not the same thing but pretty close to a post install script: it's very likely to run.

It's very naive to believe the "no influence" part. I will never give to Ladybird given their closeness with fascists. Is that the kind of influence they expect?

If you are interested in new browsers / web runtimes, Servo publishes binaries monthly: https://servo.org/download/

Probably because they don't leverage cosmetic filtering yet: https://docs.rs/adblock/latest/adblock/struct.Engine.html#me...

I encourage you to read the short paragraph at https://www.w3.org/TR/html-design-principles/#priority-of-co...

> Perhaps, but in fairness the project was started in 2018 when Rust was still new and unproven.

Rust was already proven in 2018, and I'm pretty sure they went with C++ for other reasons.

You can't compare the choices made to evolve a >20 years old codebase with a brand new one. Firefox also as Rust support for XPCOM components, so you can use and write them in Rust without manual FFI (this comes with some baggage of course).

The Ladybird devs painted themselves in a corner when choosing C++ for a new web browser, with many anti-Rust folks claiming that "modern C++ was safe". Well...

Did you factor in the highest cost of life (including housing, healthcare, retirement, etc.) in the US in your 50% ?

WhatsApp was using libsignal (the C version) when I worked on the KaiOS integration in 2017/2018.

This is a cool project, and to render Simon's blog will likely become the #1 goal of AI produced "web browsers".

But we're very far from a browser here, so that's not that impressive. Writing a basic renderer is really not that hard, and matches the effort and low LoC from that experiment. This is similar to countless graphical toolkits that have been written since the 70s.

I know Servo has a "no AI contribution" policy, but I still would be more impressed by a Servo fork that gets missing APIs implemented by an AI, with WPT tests passing etc. It's a lot less marketable I guess. Go add something like WebTransport for instance, it's a recent API so the spec should be properly written and there's a good test suite.

Some people looked at some of the authors background:

https://gameboat.bearblog.dev/the-resonant-computing-manifes...

There are actually things to be very skeptical about.

Some people are also opposed because of the negative externalities when building and running AI systems (environmental consequences, intellectual property theft), even if they understand that agentic coding "works". This is a valid position.

Mozilla Corp. has > $1B in the bank. Their pockets are not empty.

The billion laughs attack has well known solutions (basically, don't recurse too deep). It's not a reason to not implement DOCTYPE support.

> I can get the source of the kernel, including all drivers, running on my android phone with a few clicks and build a custom ROM.

No, most drivers are closed source and you can just extract binary blobs for them. They run as daemons that communicate through the binder ipc - Android basically turned the Linux kernel into a microkernel.

According to Mozilla's own data at https://data.firefox.com/dashboard/hardware Windows (7, 10 & 11) make up 84% of their user base.

Most of Firefox user base has always been on Windows, not Linux. What OS do you think the "techies" that promoted Firefox to replace IE in the first place were running?

Indeed, I did not see that!

No, the phone variant of HarmonyOS runs on top of a Linux kernel.

It is absolutely Google's security issue if they use an open source project with that license:

https://git.ffmpeg.org/gitweb/ffmpeg.git/blob/HEAD:/COPYING....

and then expect volunteers to provide them fixes.