Cl-webkit Alternatives

Similar projects and alternatives to cl-webkit

nyxt

150 9,509 9.9 Common Lisp cl-webkit VS nyxt

Nyxt - the hacker's browser.
VimFx

4 1,403 6.8 CoffeeScript cl-webkit VS VimFx

Vim keyboard shortcuts for Firefox
InfluxDB

www.influxdata.com
sponsored

Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
native_messenger

4 29 4.4 Nim cl-webkit VS native_messenger

Native messenger for Tridactyl, a vim-like web-extension.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better cl-webkit alternative or higher similarity.

Suggest an alternative to cl-webkit

cl-webkit reviews and mentions

Posts with mentions or reviews of cl-webkit. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-01-29.

Nyxt browser: mouseless copy/paste
6 projects | news.ycombinator.com | 29 Jan 2021

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.