nyxt VS cl-webkit

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!

A welcome critique, though unfortunately mostly incorrect :-D! I'll address some of your comments:

1. Nyxt is entirely written in Common Lisp, so yes, any part of it can be reprogrammed at any time. All of our FFI bindings are also written in Common Lisp (https://github.com/atlas-engineer/cl-webkit). In fact, you can even GENERATE bindings at run time. So it is irrelevant what part is invoking C, it is still fully funcall'able at runtime. This is what makes Nyxt not a 'thin veneer', but rather a deep integration which exposes all resources to the end-user (something unique to Nyxt).

2. Our project is a chrome that is agnostic of the renderer engine. We can use both WebKit and Web Engine (Chromium). This makes us resilient to renderer specific problems. If websites decide to ban browsers that utilize WebKitGKT+, we'll have another renderer available to us. We talk about this in our article where we justify some of our technical design decisions: https://nyxt.atlas.engineer/article/technical-design.org

3. Security is very important to us. We rely on upstream providers of web engines (WebKitGTK+, Qt WebEngine) to test and audit secure web engines for us. We can't do everything, you're right about that. For this reason, we give users the choice, and hope for the best!

4. "Lack of flexibility and power"- I think this point is probably the most inaccurate. If you look through our articles you'll see a couple of things that make Nyxt powerful and flexible.