alexsidorenko.com
22 posts
1,088 followers
25 following
Getting Started
Conversation Starter
comment in response to
post
Also, I haven't detected that influence in Dune to be honest 😅 At least not in the movies
comment in response to
post
I heard that Frank Herbert was influenced by Alan Watts (taoism/zen buddhism) when writing Dune. Not sure if it was the primary trigger for writing it, though
comment in response to
post
Yep, and RSC makes "invalidate everything" much cheaper. And yet, there are still cases when client-side cache is a must (e.g. dashboard with cards => revalidate one card without revalidating others)
It would be great if RSC covered this use case
bsky.app/profile/alex...
comment in response to
post
Even then, you may have a dashboard with multiple cards and want to revalidate each card separately without revalidating all the others.
comment in response to
post
Nothing is blown away in terms of client state persisting, but revalidateTag/revalidatePath re-renders entire RSC tree from the root including layouts (and refetches everything in them). Ideally, there should be a way to revalidate the page segment separately (similar to navigation)
comment in response to
post
Next is working on some sort of selective revalidation.
But yea, even something like "revalidateSegmentPage" could help, as right now it's only revalidatePath/revalidateTag, which both re-render the entire RSC tree from the root, including all layouts
comment in response to
post
Yep, that's the missing bit in existing implementations rn
bsky.app/profile/alex...
comment in response to
post
But I feel like it's nuanced, as RSC makes "blowing away your entire page" a viable option in many cases.
Anyway, it would be awesome if you could clarify how RSC compares/integrates with existing client-side data fetching libs in your write.
comment in response to
post
One thing that I noticed is that people just habitually default to Tanstack Query for data fetching when using React. And in this case, RSC sorta stays in the way instead of helping.
On which Tanner pointed out (rightly so, imo) that you still need selective revalidation from the client.
comment in response to
post
Ryan is the 🐐 of talks
comment in response to
post
Reddit is being Reddit 😅 Anonymous (no reputational damage) = more unfiltered, honest feedback, but allows arguing while being wrong
P.S. "You’re right that such leaves could in principle be HTML-only"
Oh, this is very interesting 👀
Is this optimization planned?
comment in response to
post
Is selective revalidation conceptually possible with RSC? Say, I have a dashboard with 4 charts (each is a separate server component), and I want to revalidate only the 2nd one without re-rendering the entire page on the server.
comment in response to
post
What was your previous metaphysics?
comment in response to
post
👏
comment in response to
post
Yep, makes sense
comment in response to
post
30 fps 😢
comment in response to
post
Delba's videos are sick