bobae 보배
@bobaekang.bsky.social
a corporate software eng!neer @netflix, ex-@spotify
imo "serialized components" wouldn't work for the "two worlds" mental modal
i'm obviously biased here but i'm still for the react server + component formula. this works for server functions too (i.e. there's a react server on the other side to respond to "use server" calls)
i'm obviously biased here but i'm still for the react server + component formula. this works for server functions too (i.e. there's a react server on the other side to respond to "use server" calls)
May 8, 2025 at 9:43 PM
imo "serialized components" wouldn't work for the "two worlds" mental modal
i'm obviously biased here but i'm still for the react server + component formula. this works for server functions too (i.e. there's a react server on the other side to respond to "use server" calls)
i'm obviously biased here but i'm still for the react server + component formula. this works for server functions too (i.e. there's a react server on the other side to respond to "use server" calls)
aha! thanks for the pointer! nextjs.org/docs/app/bui...
i'm still on pages router at work so didn't realize it. makes total sense for router supporting RSC to provide built-in refresh API
i'm still on pages router at work so didn't realize it. makes total sense for router supporting RSC to provide built-in refresh API
Building Your Application: Caching | Next.js
An overview of caching mechanisms in Next.js.
nextjs.org
April 23, 2025 at 2:30 AM
aha! thanks for the pointer! nextjs.org/docs/app/bui...
i'm still on pages router at work so didn't realize it. makes total sense for router supporting RSC to provide built-in refresh API
i'm still on pages router at work so didn't realize it. makes total sense for router supporting RSC to provide built-in refresh API
a "you might not need" for each 🙏
April 23, 2025 at 2:07 AM
a "you might not need" for each 🙏
iiuc, an individual server component wouldn't just re-render on its own unless the react server re-evaluates server tree on initial request or subsequent navigations?
maybe we "navigate" to the current route?
maybe we "navigate" to the current route?
April 23, 2025 at 1:55 AM
iiuc, an individual server component wouldn't just re-render on its own unless the react server re-evaluates server tree on initial request or subsequent navigations?
maybe we "navigate" to the current route?
maybe we "navigate" to the current route?
here's the syntax RSC episode on yt: youtu.be/1QXqWQ0yNfg
React Server Components: Where are we at?
YouTube video by Syntax
youtu.be
April 22, 2025 at 12:59 AM
here's the syntax RSC episode on yt: youtu.be/1QXqWQ0yNfg
sure, react server and react client are not official terms, but i really believe this model clears out most conceptual confusions while staying simple and true to the official vision
bobaekang.com/blog/rsc-is-...
bobaekang.com/blog/rsc-is-...
RSC is React Server + Component | bobae kang
React Server Component is best understood as React Server + Component, not React + Server Component.
bobaekang.com
April 22, 2025 at 12:57 AM
sure, react server and react client are not official terms, but i really believe this model clears out most conceptual confusions while staying simple and true to the official vision
bobaekang.com/blog/rsc-is-...
bobaekang.com/blog/rsc-is-...