Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
christianalfoni
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4 ms
·
1.
▲
Let us replace community with AI
(marketplace.visualstudio.com)
3 points
by
christianalfoni
4mo ago
|
3 comments
2.
▲
by
christianalfoni
4mo ago
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 verbose plans nobody really reads. It creates a world with less hu
3.
▲
Impact BETA invitation – React nested stores
(youtube.com)
1 points
by
christianalfoni
2y ago
|
1 comments
4.
▲
by
christianalfoni
2y ago
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
5.
▲
by
christianalfoni
2y ago
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 management :-D But as I understand here you basically want th
6.
▲
by
christianalfoni
2y ago
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 becomes the bridge between the reconciling world of React an
7.
▲
by
christianalfoni
2y ago
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, react-query and custom hooks. Impact does support a new ty
8.
▲
by
christianalfoni
2y ago
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 signals you access in the component. This "Obs
9.
▲
Complex state management in React [video]
(youtube.com)
3 points
by
christianalfoni
2y ago
|
9 comments
10.
▲
by
christianalfoni
2y ago
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 least has some relevant perspectives.
11.
▲
by
christianalfoni
6y ago
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 ties into friction. Everything from the experienc
12.
▲
by
christianalfoni
6y ago
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 ( https://cerebraljs.com/ ) was develope
13.
▲
Cerebral – Declarative state and side effects for popular JavaScript frameworks
(cerebraljs.com)
17 points
by
christianalfoni
9y ago
|
9 comments
14.
▲
by
christianalfoni
11y ago
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. When I say "global state" I mean the actual state,
15.
▲
by
christianalfoni
11y ago
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 object you only have to read one file to understand the com