this uses a C++ rendering engine

so what ? the parent asked for a web browser. nyxt is rendering-engine agnostic by design

otoh how much rust is there in firefox? a:

https://4e6.github.io/firefox-lang-stats/

the hard part about a web browser is the rendering engine, which is why it was raised as a challenge. Sticking a Lisp front end over an existing rendering engine doesn't answer the challenge.

then he didnt ask the right question. nyxt is a browser in every sense of the word. anyway there is no reason lisp cant be used for making a good rendering engine

Here's a browser written in pure Common Lisp: https://closure.common-lisp.dev/

These questions are so silly. Nobody's written a web-browser in Rust, Python, Ruby, Java, Clojure, Haskell, Erlang, Typescript, Javascript, etc. but that hasn't stopped anybody from using them.

Just admit you don't want to learn Lisp.

Doesn't support HTML5, CSS3, JS. Non-starter.

I learnt Lisp sometime around 1986 (from library books and later, on the Sinclair QL LOL), I do love it in some ways, but found distribution of final code to be an issue. I don't think it's suitable for all tasks.

> but found distribution of final code to be an issue

in 1986 ?

> don't think it's suitable for all tasks

to this day im yet to see an example of a software engineering problem that lisp is not suitable to solve. if you have such an example ready i would be genuinely curious. otherwise its just a thought from a very common and lazy misunderstanding of what lisp actually is

im talking about computational problems. things that are non-examples include such things as business sense/requirements, availability of programers, availability of ready made libraries/frameworks, or claims of apparent unsuitabilty in large teams