wayne VS LIPS

Just created a Server-Sent Events Proxy with my Open Source library Wayne. This was the last open issue on GitHub.

This is not in any way useful, but I thought it's a cool hack that you can render ReactJS inside a Service worker and serve routes as HTTP requests. This is a showcase of my Open Source library Wayne.

This a demo of few of my Open Source projects I'm maintainer of: * Wayne - Service Worker HTTP Router * jQuery Filebrowser (almost forget about this one, but someone created an issue recently) * lighting-fs - in Browser implementation of NodeJS fs module

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

But first a little bit of background. Last year I've create a JavaScript library called Wayne that abstract the idea of creating pure in browser HTTP requests with the help of Service Worker. The API is similar to express.js NodeJS framework, but work in the browser instead of the server.

jcubic/wayne

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.