dart VS LIPS

I wrote a similar app for archivists to push materials into preservation repositories. I used Electron, since it has good cross-platform support. The source is at https://github.com/aptrust/dart with documentation at https://aptrust.github.io/dart-docs/users/getting_started/

The underlying JavaScript code in that app started getting messy because I was working on several other projects simultaneously, but you might find it useful to play with as you consider your desktop app.

The archival community uses a simple text-based packaging format from the Library of Congress called BagIt, which allows you to include metadata and checksums with your archived materials so you can ensure their integrity and make sense of them when you get them back.

Anyway, you're working on an interesting problem. I'd be interested to see how it goes.

Sweet, I'll have to give that a go :)

Another option in browser land is lips[0], which exclusively targets a js backend.

[0] https://lips.js.org

For Scheme implementations there are LIPS and biwascheme. I haven't done more than play around with them, so I can't really give an informed opinion about pros and cons or favorites.

Your example revealed a bug in my Scheme interpreter. This is an example that fails to match:

In my interpreter, LIPS Scheme, vector literal syntax is created using a syntax extension, a token that is mapped to a function or a macro. So you can use things like this:

I'm not sure about other Scheme interpreters but in my interpreter LIPS Scheme, there is (env) function that returns a list of symbols. You can also access environment objects e.g. (current-environment) return object that is used internally. And you can even access the scope chain because the env object has __parent__ property that returns the parent scope.

Few of my Open Source projects: * jQuery terminal * LIPS Scheme * Gaiman * Sysend * Wayne

(define promise (--> '>(fetch "https://lips.js.org/") (then (lambda (res) (res.text))) (then (lambda (text) (. (text.match #/\s*([^>]+?)\s*<\/h1>/) 1)))))

ngl when I first saw the headline my first thought was, “Wait, bring CAR into JavaScript? Make it a Lisp? But hasn't it already been done?”

Languages like Biwa Scheme and LIPS Scheme are good for running Scheme in the browser. But I would prefer compiling Scheme code to JavaScript in the server, then serving the compiled JavaScript image to the browser.