Hacker News Reader

Comment by aenero | Hacker News Reader

I'm one that loves simplicity in things. So despite the plethora of state management libraries for React, I have always wondered what the absolute "simplest" approach would be.

I wrote this library with the hope that this might be it. Any ideas/suggestions how to further simplify it would be super!

View on HN

I really like what you have done here. I have two questions:

1. Do you mind sharing examples with async calls? This is very common and I really look for this example as quick as possible

2. How you do connect two stores? Say one triggers and update in the other...

Thanks a lot :)

You'd be happy to know those are supported and documented at https://simpler-state.js.org

Specifically, look at these "Recipes" pages:

https://simpler-state.js.org/recipe-async.html

https://simpler-state.js.org/recipe-orchestrators.html

It’s not clear how to define a new entity out of another one using a selector. So perhaps instead of/in addition to `x.use(foo)` you might want `x.select(foo).use()`.

Not sure if simpler but something I’d be missing/would feel inconsistent.

Hi. SimpleR State makes use of selectors without creating a new entity (unlike atoms in Recoil, for example). It uses the more classic paradigm used by popular libs like React Redux where you just use selectors to filter/transform the "received" state to the format required by the component, and not to "create" a derived state per se. I hope it makes sense.

Looks kind of similar to something Mithril does (or used to do). Ergonomically, I prefer `counter(0)` to `counter.set(0)`.

Reply on news.ycombinator.com