beacon VS nyxt

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 not exactly the same audience, one may find the Dockerfile for building Beacon handy as (a) more code, less talking (b) since Beacon is just a patched Chromium, its dependencies should be a superset of vanilla Chromium

Why are you swallowing "error" from invoking the "reall" tool? That seems like a great way to make contributors really frustrated: https://github.com/imperviousinc/beacon/blob/main/tools/src/...

and again https://github.com/imperviousinc/beacon/blob/main/tools/src/...

This trend of "I'm going to invent some build tool because there are not enough build tools in the world" is evidently leaking out of the node ecosystem

For clarity, I did see that this was inspired by the brave-browser model, but of the ones to draw inspiration from, that's for sure not it given that their CI is closed source and they're trying to use npm in lieu of a more structured, comprehensible system

I like trying out alternate browsers, so congratulations on the launch, and I'll for sure try to build it, but I wanted to draw these to your attention because my experience with software is that error handling is about 80% of the job

If someone invents another browser, Nyxt will be ready to wrap it with Common Lisp: https://github.com/atlas-engineer/nyxt

I can't reproduce the bug report on flatpak. Bug reports should be reported at https://github.com/atlas-engineer/nyxt/issues/new/choose.

For innovative new browsers, there's Nyxt: https://nyxt.atlas.engineer/

Both are looking for funding and sponsors.

good idea. I know there are some plans for this underway.... looks like just planning phase right now. https://github.com/atlas-engineer/nyxt/issues/3095

I am not a hopeful romantic, but the EU has been investing on vendor neutral web-browsers like Nyxt [0] and the UR Browser [1] through the Horizon Europe program. I doubt that legislators (at least in the EU) will view this as a positive development, assuming EU legislators know what they are doing. On the other hand, lobbying by big tech is still very much a threat.

[0] https://nyxt.atlas.engineer/

[1] https://www.ur-browser.com/en-US

There are some keyboard centered browsers like Qutebrowser or Nyxt. For Firefox as well as for Chrome based browsers there exist several extensions to implement vim-like keybindings.

Am I correct that this is not fixed until this issue is closed (I tried building from source the 3.3.0 release and master branch but both have the exact same issue)?

Go to the website -> Download -> Download for GNU/Linux -> Get Nyxt for GNU/Linux!