Viewing profile — christianalfoni

We are all feeling the pressure of generating code with AI for short sighted productivity gains. And with that the increase of cognitive debt, constant context switching and verbos…

Built on React context, use any reactive primitive you want and get concurrent safe, automatic observation in components and fast refresh support for your stores

Ah, I see! I have not worked much with RxJS observables, though I did implement dark/light mode on their previous website... and wrote some docs on how to use them for state manage…

Yeah, I agree that is definitely a tall ask :) I just published a version with the signal props. Doing this made me realise that it creates this strong concept that StoreProviders …

Hi again and thanks for this discussion :) Yes, what you are saying makes a lot of sense. And traditionally you would need to do some combination of a global state store like Redux…

Hi Sebastian and thanks so much for your feedback :) 1. So with observation an `ObserverContext` is created when using a store in a component. This "ObserverContext" tracks what si…

Impact is currently in release candidate and aims to solve some key pain points moving to global state management. With React 19 and new async patterns this library at the very lea…

Exactly! :) It is very difficult to convey "When does this solution pay back its cost". If you can get by with only React as state management, great. There are so many factors that…

Hi there and thanks for the feedback on "Why even choose this". Will update the front page! But to answer your question. The main reason Overmind and its predecessor Cerebral ( htt…

This is really interesting, we have very different perspectives on how to consume how an application works. Not saying you are wrong at all, just have different perspective :) 1. W…

Hi there, I do not quite agree with this. Though I acknowledge your sentiments :-) 1. Global state is easier to reason about. If you have a single state store expressed as a single…