ladybird VS quickjs

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!

You may be familiar, but I just wanted to show how it is available in many C implementations and is used, for example, in QuickJS: https://github.com/bellard/quickjs/blob/0c8fecab2392387d76a4...

It uses service workers to cache static files, by the time it opens up you already free to be offline, try toggle network switch to verify.

It has download link at bottom of the about page ([accdoo.app/about]) which you could then self host it by dropping into any static hosting services.

btw, the Pi feature was by-product from the original App but I won't expand here, if you'd like to learn more, please checkout its two Show HN post (39115559 and 39138957) previously.

[wiki]: https://en.wikipedia.org/wiki/Chudnovsky_algorithm

[quickjs/pi]: https://bellard.org/quickjs/pi.html

[pi_bigint.js]: https://github.com/bellard/quickjs/blob/master/examples/pi_b...

[accdoo.app/about]: https://accdoo.app/about#releases

[39115559]: https://news.ycombinator.com/item?id=39115559

[39138957]: https://news.ycombinator.com/item?id=39138957

Just go with quickjs, I think this is what you are looking for.

https://bellard.org/quickjs/

QuickJS

I think QuickJS, written in C, is a user-"friendly" starting point for implementing ECMA-262. Documentation QuickJS Javascript Engine.

There is a readme on the project's main page: https://bellard.org/quickjs/

The newsworthy bit here is that the activity seemed to have stalled for year or two and now Fabrice pushed a few fixes and made a new release.

Just to demonstrate GitHub repositories do not necessarily reflect upon a programmers' body of work, Fabrice Bellard has one (1) repository published on GitHub, quickjs. Compare the list of work on Bellard's home page https://bellard.org/.