Loving your approach to explaining RSC so far!
How about “live data” in this scenario? Eg. say you wanted to constantly stream new comments and show live likes count on each one. Wouldn’t you need to switch to a very different fetching mode?
How about “live data” in this scenario? Eg. say you wanted to constantly stream new comments and show live likes count on each one. Wouldn’t you need to switch to a very different fetching mode?
June 1, 2025 at 3:41 AM
Loving your approach to explaining RSC so far!
How about “live data” in this scenario? Eg. say you wanted to constantly stream new comments and show live likes count on each one. Wouldn’t you need to switch to a very different fetching mode?
How about “live data” in this scenario? Eg. say you wanted to constantly stream new comments and show live likes count on each one. Wouldn’t you need to switch to a very different fetching mode?
Amazing post!
I wonder if naming React Server Components as “ViewModels” (for real) would help with understanding and adoption. Sure, it’s not as elegant as “component”, but practically they are different enough in important ways, and pointing to similarities only adds confusion
I wonder if naming React Server Components as “ViewModels” (for real) would help with understanding and adoption. Sure, it’s not as elegant as “component”, but practically they are different enough in important ways, and pointing to similarities only adds confusion
April 16, 2025 at 10:05 AM
Amazing post!
I wonder if naming React Server Components as “ViewModels” (for real) would help with understanding and adoption. Sure, it’s not as elegant as “component”, but practically they are different enough in important ways, and pointing to similarities only adds confusion
I wonder if naming React Server Components as “ViewModels” (for real) would help with understanding and adoption. Sure, it’s not as elegant as “component”, but practically they are different enough in important ways, and pointing to similarities only adds confusion