It seems like the evasion / accuracy die is working a bit like armor with a dynamic value?
It seems like the evasion / accuracy die is working a bit like armor with a dynamic value?
Iβm very curious about this one
Our reactivity was lazy too. In practice that didnβt matter when you rendered a large list of reactive tasks.
Are there any times where you feel like you know more than Opus? Eg are you providing value add by steering the model?
That makes sense. I was thinking about building a local first app so I don't even need SSR. I'd use TanStack Query to just load the data from IndexedDB
@jovidecroock.com do you have a perspective on the ideal Preact stack these days? I imagine some combo of ISO Router, Tan Stack Query, Signals?
Thatβs really cool! I had not noticed that in the API before. I had been doing a similar thing with classes by making the signals private properties and exposing getters / setters for them.
Yeah, I think this was one of the core issues with how Luna 1 worked. Everything was a fine grained leaf including responses from the server and all component state so the graph was very large.
Totally agreed. Do you have a sense of the practical size limits for Preact Signal's graph? E.g. are there best practices of when store an object as a signal vs an object of signals? Same for collections?
I really enjoyed programming in it and want Signals to work. (I use Preact Signals in side projects, itβs great!) I just worry about repeating the patterns that drove us to rewrite Asana.
So we would setup and tear down large dependency graphs that would never be leveraged by the user because of their behavior. Also many of our engineers struggled thinking about frequently their computed out effect function would be triggered by dependent inputs.
We did end up moving away from fine grained reactivity due to performance though. We built our entire framework around Signals (it looked a bit like Solid and was the inspiration for Meteor). In practice, we didnβt get the fine grained reactivity benefits. Users would load a page and navigate away.
Yeah, Iβm not saying the model is entirely broken. Just that users need to know about those edge cases. We wrapped time and other mutable globals in Signals to help. Kinda like the useSyncExternalStore of Signals.
Asana built a whole framework on Signals in 2009 that we eventually moved on from. There are a few other issues that can cause bugs. If you use a non signal value in a conditional that can cause issues as well (e.g. time or randomness). These issues also apply to computed signals too right?
Can you make it so that the bottom of the subtitle aligns with the tip of the sword?
Whatβs the subtitle?
I like the sword of the pixel logo but the glow and smoothness of the word
Cool! That type of project has always been my dream side project.
@rpdeshaies.farirpgs.com what is Free Blade?
Iβm so excited! Given that you donβt want to build transitions / form actions, do you see Preact diverging more from React?
Yeah, Iβm curious as well.
Thatβs one of the ways I get Claude Code to work on CODEZ. One session in plan mode to come up with the idea. Another session to critically review the plan. (Then another session to implement. Another session to ask it to make a new plan to break it down. And a session per step for stacked PRs)
Why did adding ONE component make your build drastically slower?
The answer is often: Barrel files.
Luckily, you can enable Lazy Barrel Optimization in @vite.dev 8 and @rolldown.rs do bring your build time back to normal.
Want to know more? Check the video & docs
rolldown.rs/in-depth/laz...
Iβm not sure either but I know you make great solo games so I figured I would ask π
Have you thought about solo Wyrm at all? The system seems like it would be able to handle it well
That makes sense, thanks for sharing
Yeah, I think the goal would be to make it easier and the path of least resistance for folks. Related, do you know if Preact will support form actions too?
Cool, those are the ones I usually look at too. My dream would be able to lazy load the component for the route but prefetch the query key so you can load the data and the code in parallel. Maybe I can add a PR to add it to one of them π€
This is so exciting! Is there a router you recommend with Preact / Preact Query?
Fellow alum Scott Carleton and I built an Asana client designed for AI coding agents like Claude Code. It's a fast, reliable alternative to MCP tools.
β Search/create/update/comment on tasks
β Manage goals, custom fields, dependecies, and more
github.com/dmoskov/sharedskills/tree/main/asana