Artist, programmer, and solo indie game dev

Joined December 2011
78 Photos and videos
Robbie Speed retweeted
The best way to use AI is an interface to information that lets you deepen and improve your own knowledge and mental models. The worst way to use AI is as a crutch to outsource and forsake your own cognition
102
240
1,995
89,772
I'd like to see AI coding tools treat the user as less of a manager/reviewer. A good tool should know how to act as a manager and when to delegate some of the complex programming and architecture tasks to the user.
1
1
94
LLMs are still shit at reviewing, but it's easy to spot what parts of the review are bogus (so long as you understand the code), and you can be left with them spotting a legitimate bug.
86
Some people really seem to like these signal things... What if Remix could do fine grained reactivity too?
5
9
1,528

Actually you don't even need to wrap the render fn if all the signals are passed rather than consumed in the render like the example. So this works too.
1
484
Yes you can use "real" signals in Remix 3 stackblitz.com/edit/vitejs-v…
11
3
69
11,147
Thanks to @sergiodxa for the inspiration x.com/sergiodxa/status/19788…

Next on @remix_run v3 state management libraries, I tried @preactjs Signals core package. This requires to run the effect to subscribe to the signal inside this.queueTask, otherwise it tries to re-render before Remix did the first render. Full code: github.com/sergiodxa/remix-v…
2
1,044
It will be very interesting if (or when?) Remix 3 announces support for async function components.
1
8
4,250
Remix 3 render model has a lot of similarity to Crank.js. What I didn't see was how updates to props are handled. I'm guessing they had to make the same trade-off, but it's worth it for a a simple render model that doesn't have the pitfalls of storing state inside a render block.
1
7
447
Nvm just watching @mjackson hydration part of the talk and see that he shows update props in the render function which is what I was expecting.
2
111
2026 will be the year web browsers implement tail call optimisation in CSS.
2
213
What if you could use the same reactive data flow primitives for server, client, and even AI orchestration?
2
2
462
Taking it a step further you wouldn't need Agents\.md or .cursor/rules, you could manage your coding agents the same way you write the rest of your code. The agents could also be instructed to update their own flows, and you'd retain a deterministic view of the data flow.
1
260
It only takes 160 lines to build a system supporting a node tree with reactive hooks.
"Explain to me how useEffect works"
1
1
435
Beauty of Balanced Ternary
1
186
When I look at reactivity what I see is the graph. It's been that way for me since my early days with ember when reactive dependencies were explicit. Today most reactive libraries (ember included) make this very hard/impossible since they treat dependencies as implicit.
1
1
5
601
Ember's approach wasn't perfect. Reactivity was restricted to object properties, like React hooks dependencies were static and declared in both dependency list and logic. Solving these issues doesn't require throwing out visibility of the graph.
1
147
Reactive dependencies can be explicit without being static. You don't need hidden global state to track what reactive values link together on the graph.
1
113