Galactic-State VS LIPS

I created my own “global state” management library: https://github.com/baron816/Galactic-State. It takes 30 seconds to learn, is very lightweight and ergonomic, and should solve performance issues with Context. Please check it out.

I'm working on a simple state library for React. It will 1) allow you to have a "global" state that doesn't require context [1], and 2) allow you let you set state imperatively [2].

The links below are the two separate parts that I want to combine together so that you can have that imperative state setting apply to all components depending on the generated hooks. That's the easy part.

`useStructure` allows you to have a class that your component uses for state (and be able to use any methods on that class). The hard part will be having async functions on those classes that update your state correctly. Not sure if it's even possible.

[1] https://github.com/baron816/Galactic-State

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.