> Hi, I am one of the developers. You seem to be mistaken, it is not a WebKit shell (we are currently working on a web engine variant). It is actually a standal

> Hi, I am one of the developers. You seem to be mistaken, it is not a WebKit shell (we are currently working on a web engine variant). It is actually a standalone Lisp program that defines a protocol for client browser implementations. OK, looking through the README in the ports/ directory, I see this: > Next is made of two programs: > The Lisp core which offers the user full control over the browsing. It’s 100% Common Lisp. > The “platform port”, which only purpose is to display a window with two components: the minibuffer and the web view. > The two parts communicate via D-Bus, an RPC system. The Lisp core sends a D-Bus request to the platform port (for example, “open this URL”); the platform port acts upon it and sends a D-Bus response back to the Lisp core. So you've put the WebKit stuff into another process, but your browser is WebKit based, unless I completely misunderstood what I just read. You couldn't use Next to drive Firefox, for example, without some interesting re-writes on the Firefox end. (Just to make it abundantly clear: I think this is a really neat hack and a good way to separate concerns, but the way you phrased things confused me until I dug into the README you linked to and read some source code.)