Mike Pearson

I remember seeing this at one point. I need to fix up this example. I didn't create it originally. But I think I only saw this when creating a prod...

Well I ended up on here and this worked for me. I was trying to do: ``` interface Data { [index: string]: number; } interface WithSpecialProperty { specialProperty: string; }...

@tomastrajan is exactly right: > If we directly wire events to the store, there is no huge difference between dispatching an event and calling a store method. There's a great...

> I never wanted to create a state management library. Note to anyone reading afraid I'm going to drop StateAdapt support or something: I won't stop pushing StateAdapt aggressively until...

With events, any chance of Redux DevTools visibility for signal stores? And if events can't be treated as events and are just extra decoupling between components and state changes, is...

This is funny. React devs don't like the dependency array of useEffect. Ryan Carniato painstakingly invents a pattern of auto-tracking. Angular copies Solid signal pattern. Angular community reinvents dependency arrays.

1) I could see some devs getting tripped up by this 2) This is generally a sign of really weird data flow 3) Am I the only one who even...

> What's wrong about having both options - explicit and implicit dependency tracking? It's easy to say that supporting more options is always good. But the most valuable thing we...

Of course the implementation is different, but the auto-tracking _syntax_ was intentionally copied. Solid effects also auto track dependencies. I really don't see how the implementation details are relevant. >...

> An overwhelming majority of people I've talked and listened to said that untracked is something they always use. To me this is a huge red flag. What are they...