unobin VS LIPS

I'm working on tool called Unobin that lets you write Ansible-esque playbooks and compile them to a standalone binary with all of the templates and files baked in.

I'm trying to solve the "works on my machine" problem that's very prevalent in the devops world. One person's playbook (or Terraform module or Chef cookbook or whatever) works fine on the developer's machine due to assumptions made during the development. But transfer that code to another machine and it's a whole 'nother story. There is often a lack of rigor around dependency management and versioning, along with hidden dependencies such as programs that need to exist on the machine where the playbook is run. I want to make it possible to include all of the dependencies directly in the binary, so you truly need just one binary (unobin) to download and run.

I've made a lot of progress and have what I feel is a solid POC at this point. It lacks many modules but I'm just writing them as I need them. Right now I'm working on a reference playbook to build a Concourse CI stack, and that's giving me solid feedback to myself about what's missing.

https://github.com/cloudboss/unobin

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.