3 ms·
Note that this appears to be yet another Webkit shell, and not an implementation of parsing/rendering pages in Lisp.
by userbinator 7y ago
Note that this appears to be yet another Webkit shell, and not an implementation of parsing/rendering pages in Lisp.
- Koshkin 7y agoWhich is good, otherwise web pages might look like lisp.
- _emacsomancer_ 7y ago> Which is good, otherwise web pages might look like lisp. (what-is-p wrong (with 'that)) More seriously, there's also the security angle with browser, that using an independently developed engine has certain advantages.
- mepian 7y agoThe latter is a hell of of a task, given the complexity of the current web standards. I'm not sure if it's possible to do this decently without some kind of serious financial backing.
- userbinator 7y agoTargeting a subset, i.e. the "document-centric web" (no JS, only basic HTML and CSS), is not that difficult in comparison and has been done by a few others; the most prominent of these "second tier" browsers being https://en.wikipedia.org/wiki/Dillo https://en.wikipedia.org/wiki/Dillo and https://en.wikipedia.org/wiki/NetSurf https://en.wikipedia.org/wiki/NetSurf . Of course, writing a text-based browser in Lisp or any other language is far simpler but also less practical.
- jmercouris 7y agoThis is certainly possible with our current architecture. Maybe we will do it at some point down the road.
- RodgerTheGreat 7y agoI've been looking for a lightweight browser I can use on older machines- Dillo and NetSurf both seem worth checking out!
- c256 7y ago> Of course, writing a text-based browser in Lisp or any other language is far simpler but also less practical. Emacs has a few; the included one is called “ewww”, and is pretty nice if you’re into emacs already.
- BubRoss 7y agoThen there shouldn't be claims of a web browser written in lisp when that isn't the case.
- deleted 7y ago[deleted]
- lelf 7y agoRendeting is done in WebKit [on macOS], that’s correct. But it’s already a lot more than a “Webkit shell”, e. g. see https://github.com/atlas-engineer/next/blob/master/source/remote.lisp#L405 https://github.com/atlas-engineer/next/blob/master/source/re...
- jmercouris 7y agoHi, 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. Please see the following file for more information: https://github.com/atlas-engineer/next/blob/master/ports/README.org https://github.com/atlas-engineer/next/blob/master/ports/REA... Eventually we would like to make our own web-renderer, but we recognize that it is a lot of work, and a bit away
- deleted 7y ago[deleted]
- msla 7y ago> 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.)
- bryanrasmussen 7y agoI wonder if you could do what remote browser does and drive Firefox by the web extensions api, https://github.com/intoli/remote-browser https://github.com/intoli/remote-browser.