Daniel Saewitz

I'm building my own RSC web framework, so I did a deep dive into RSC rendering performance. What I found was a roughly 10x performance hit compared to the classical `renderToString`. Some cost is ofc to be expected. github.com/facebook/react…

if you would like to read it saewitz.com/coding-is-chan…

From my article on agentic coding written last July...

@infinterenders yeah but good global state

url is global state

@jordwalke this is why I built driver github.com/switz/driver

Hey man, do you mind if we push this call til next week? I’m thinking one or both of us might die in the upcoming nuclear holocaust, which would pretty much solve this whole problem for us

new homepage animation. pure css, no javascript saewitz.com

@ngeloxyz @nilansaha @Railway @vite_js @tan_stack @vrzgc just curious - did you run into any issues with tanstack? have you guys ever tried server components or the app router paradigm?

@nilansaha @Railway @vite_js @tan_stack @vrzgc fun fact, blog. - this is actually not on Tanstack, guess we gotta migrate that too ;)

We moved Railway's entire frontend off Next.js. Two PRs, zero downtime. Builds went from 10+ minutes to under two. 200+ routes on @vite_js + @tan_stack Router, instant HMR, and dev server startup in seconds. @vrzgc's full breakdown: blog.railway.com/p/moving-railw…

@DavidKPiano no, i'm just joking. but 'jsxstate' is right there

@switz213 Eh do we really want that?

Thinking about making machines more composable in the next version of XState Instead of just invoking, you can also "compose" it directly as a compound state, with its own isolated context. Its states & events become part of the parent machine. What do you think?

7 months ago I predicted the number of lines of code written would hockey stick I might be off by an order of magnitude

Hope this is useful and results in some upstream improvements to the rendering pipeline. I'm hoping these findings are useful & benefit the whole ecosystem.

I built (with Claude) a proof of concept fused renderer that moves the pipeline to a single walk and it showed some promising gains. This is not an indictment of RSCs (I'm building my own framework on them), it is merely an attempt to understand where the cost comes from.

I'm building my own RSC web framework, so I did a deep dive into RSC rendering performance. What I found was a roughly 10x performance hit compared to the classical `renderToString`. Some cost is ofc to be expected. github.com/facebook/react…

@JohnPhamous if the premise is – I want that page context visible – a modal isn't really the best way to show off that context for obvious reasons. it hides so much, and modals aren't really move-able. make a better inline-deletion or a page so you can open them side by side if you have to.

@JohnPhamous intercepting routes ameliorate some of the issues with modals. but that adds its own complexity and nuance. haven't found many cases where it's so worth it. instagram is the token example, and is a half decent edge case I'd say.

delete confirmation