This was really fun. I dunno if t3/t4 are based in anything specific but most of this is surprisingly sharp, while also being ridiculous. What surprises me mos

This was really fun. I dunno if t3/t4 are based in anything specific but most of this is surprisingly sharp, while also being ridiculous. What surprises me most is that we have tried so many things, except most apps are a handful of bundles, and even more wildly, almost all work happens on the main thread still! React's vdom has given us a very nice & performant Immediate Rendering (vs Retained Rendering) view, and we've dabbled with unidirectional data flow, signals, whatever graphql is, and other abstractions, but the core "where and how does work happen" model hasn't been much iterated on. Now we are very busy figuring out React Server Components and doing other page rehydration works, which indeed can shift much of the work out of main thread. But the client has been somewhat stuck, somewhat patterned into monolithic main thread patterns forever, and few have tried to push beyond that. Even with wasm happening, it still seems like few are using web workers to divide up where the work happens, which feels like it could be such a giant win for keeping the page crisp & responsive, for thickening the client effectively.