dan @danabra.mov · 22/04/2025⚛️📝 New on Overreacted: Impossible Components overreacted.io/impossible-c...overreacted.ioImpossible Components — overreactedComposing across the stack. 1619422
Damien @lookatmedamien.bsky.social · 23/04/2025As a bit of a grug-brained developer, this is the most compelling example of client/server components so far! 130
Guillaume @gfox1984.bsky.social · 24/04/2025While I understand the top-down approach of RSC, I have to say that the bottom-up approach that sync-engines are taking better clicks with me... Maybe RSC is more suitable for static(-ish) websites, while sync-engines are better suited for highly interactive web apps? 120
omothm.bsky.social @omothm.bsky.social · 23/04/2025All recent posts are brilliant—as always. Thanks, Dan! Can't wait for RSC to land in React Router! 060
Rogerio Romao @rogerioromao.dev · 23/04/2025This was amazing. Boiled down RSC to the simplest terms without even calling it that, and all the code and the mental model made perfect sense. Having not worked with RSC yet, and read a bunch of jargon heavy theoretical posts about it, I wasn't very interested. This changed it. Ty 010
Lo-fi Gaming Lounge @lofigaminglounge.com · 22/04/2025yo sick ima read it Also what weird cosmic coincidence that you picked "Alice" out of a hat which happens to be the name of my 2 year old Winners all around 130
Eva Lothian @rhalin.bsky.social · 22/04/2025👀 I did something similar to this before, with location-centric data in .Net / Vue. The major gain I was looking for was serving partials at *edge* from cache. Since it was location specific, it made individual edge caches small, and backend API could be centralized instead of distributed 140
Ryan Toronto @ryantoron.to · 22/04/2025Great post. The squiggly line that splits the server and client components is an awesome UI and makes the code easy to read. Is that new? 170
yuvalshimoni.bsky.social @yuvalshimoni.bsky.social · 22/04/2025"The backend passes data to the fronten" Wow. It's simple yet brilliant 👏 I remember trying to wrap my head around things when I switched from PHP to a React SPA. I was like, “Wait a minute... we were already on the server—why are we just getting an empty HTML page from it?” 170
Mateusz Hallala @hc-svnt.bsky.social · 23/04/2025It is rather nice now that since the boundary has expanded it actually lets react be more react, one can go on for days without resorting to side effects. You could think it should've been this way all along. 🤠 040
Mateusz Hallala @hc-svnt.bsky.social · 23/04/2025Using 16px+ font size in inpus prevents iOS zooming in on focus, please. Great article, though! Thanks. 020
Islam Naasani @islamnaasani.com · 22/04/2025great read! the <ExpandingSection /> example opens the possibility to nest server components into client ones however, how would you approach this if the server component is deeply nested? 140
Artem Zakharchenko @kettanaito.com · 23/04/2025I am wondering, the natural evolution of this API is to collocate the "server" part and client part, which is also what Next.js and Remix are doing (think server actions inlined in client components). Module-level directives is magic. So are special exports, for example. What's your opinion on it? 220
Artem Zakharchenko @kettanaito.com · 23/04/2025> Of course, we’re not limited to passing colors. We could pass strings, numbers, booleans, objects, pieces of JSX—anything that can be sent over the wire. Wait, is JSX fully serializable? Or by "pieces" you refer to the parts of JSX that actually are? 🤔 Since it may contain event listeners, e.g. 110
Angelo, o Cronofóbico @angelodias.com.br · 24/04/2025brilliant. I still have issues with some framework-specific stuff, like revalidating cache for a page to reload the backend data, but the main core of RSC has made everything so much cleaner and prettier that I'm not keen to let it go. 020
