Fantastic! Wrapping WebKit is a great idea. I mean it generally hasn't worked well for other libraries that have tried it, none of them have managed to avoid

Fantastic! Wrapping WebKit is a great idea. I mean it generally hasn't worked well for other libraries that have tried it, none of them have managed to avoid lots and lots of bugs and quirky behavior, but maybe you do, so congratulations. My only point is that this isn't a browser written in Lisp. It's not even remotely close to that! Yet that is what the title of the HN story implies. But it's not that, it's a wrapper, which is not what the title says, so I mentioned that. You are agreeing with me except you seem to think I'm implying something bad, which I'm not, beyond all the things implied by the facts, such as: It does inevitably just feel like a thin wrapper. There is no way for a lisp hacker to get in there and play with it, or take this work and extend it using lisp. They can change how WebKit is wrapped, but changing or extending WebKit's behavior means digging into WebKit's millions of lines of C++.