[creamytaco]

1. You're arguing semantics in a disingenuous fashion which reinforces my point and make me like Nyxt even less. Nyxt, the end-user product, "is not entirely written in Common Lisp". Your rendering and browsing engine, the core of your application, Webkit, is not a Lisp library.

2. This doesn't solve the problem. Being able to use both webkit and web engine in no way makes you resilient to the issue I brought up. Google has plenty of reasons to disallow and prevent their engine to be used by Nyxt and they have said that they will do so. Your answer strengthens my point.

3. Again, the issue is systemic and there's nothing upstream providers of web engines can do. Using these libraries in isolation will always expose you to significantly more security issues than using them as part of the browsers they were meant to be used in.

4. Flexibility and power (as I explained) is me using uBlock origin and coutless other extensions without reimplementing them from zero. Do you have uBlock origin for Nyxt? I rest my point.

5. Really? Then explain this: https://nyxt.atlas.engineer/applications

I'm very disappointed in your answers but I rest easy in knowing that my opinions and choice not to waste my time with your project are justified.

[jmercouris]

1. That is irrelevant, everyone depends on libraries, which are often written in different languages.

2. We don't depend upon Google, we could just as well use Servo. The whole point is that we are agnostic of rendering engine.

3. This point is unsubstantiated and false. There is no technical reason to justify this claim.

4. Supporting WebExtensions is on our roadmap, it takes some time. Please have patience :-)

5. We are building applications ON Nyxt, it is however not the purpose of Nyxt. It is just one of the many things are doing with Nyxt as platform.

Your loss :-)