And I think that’s one of the reasons I’m huge fan of performance tracks (despite easier debugging obv). It shows you how many smart things happen under the hood - people vastly underestimate React imho when they say it stagnated and it’s focused on moving to server. This perfectly shows otherwise

Maybe I’m too nerdy but this few screenshots accompanied by your description of transitions/concurrent rendering is perfect for me. It mixes technical stuff with real life use cases in really good way. I’d love similar talk

I didn’t know that I’m using Tanstack Query after work so often 😄

In general I’m kinda not sure how React imagines managing status/headers in RSC world. Because streaming is one thing and that sounds doable with solutions similar to this or stuff like RR headers. But PPR/postpone?

Yeah - that probably makes sense and that’s what I imagined. However, it feels less React-y this way - can’t articulate exactly why though, not vibing a bit.

Played a bit with it. I dislike one thing mainly - I need to be aware of whether some component that I’m trying to use calls this function or not so I lose a bit of composability/locality. Also it can easily lead to race conditions stuff where it’ll sometimes work and sometimes not.

I think that’s really cool as a low level primitive. I’m really curious how that could be used with some higher level opinionated library. Playing recently with RSC in Vite (thanks to yours RSD impl, thanks a lot) - I’m really excited about the new stuff.

Why are you manually concatenating search parameters in Tanstack Router? And converting them number<-> string? 😃 That’s one of the nice built in things in Tanstack Router that you get type safety and easy management for all of that

I’d use that 😄

I’m not fully sure what is causing it because it also sometimes happens on normal font size and doesn’t always happen on big 😄