3 ms·
How is this “Lisp-based” when it’s a wrapper around QtWebKit? I’d expect a “Lisp-based” browser to implement its rendering engine in Lisp, probably atop CLIM.
by eschaton 9y ago
How is this “Lisp-based” when it’s a wrapper around QtWebKit?
I’d expect a “Lisp-based” browser to implement its rendering engine in Lisp, probably atop CLIM. Otherwise you’re just using Lisp as a scripting language to glue a couple prefab components together.
- jmercouris 9y agoWell, that would be quite slow :D You’re right in a most technical sense, it’s a lisp programmable browser
- eschaton 9y agoWhy do you think so? Compiled Common Lisp can be quite fast.
- jmercouris 9y agoCompiled Common Lisp can be quite fast, but not fast enough. Additionally, I don't see the added value in having the rendering be done in Lisp, I'm only interested in the manipulation of the data in Lisp
- db48x 9y agoConsidering the amount of work it would take to write an HTML rendering engine from scratch, this is a perfectly reasonable way to go.
- eschaton 9y agoAnd yet WebKit came from the KDE folks deciding to do just that.
- gkya 9y agoThen Emacs does not count as a Lisp based editor too, given it's renderer is in C.
- eschaton 9y agoGNU emacs certainly isn’t a Lisp-based editor like the various implementations of Zmacs were, or like Hemlock is. It’s an editor with Lisp as a scripting language.
- lispm 9y agoI don't think that's completely right, given that much of the editing functionality has been implemented in Emacs Lisp. Emacs Lisp is as much an implementation language as a scripting language. It's just that there is another implementation language underneath...