Nice, that could be a useful pattern!

Yeah, it's a shame! When I needed this behavior, I had to add an intermediary div with
{ display: contents; --parent-value: var(--value); }

Is <Maybe> a special type or error boundary, and <PostEmbed> throws when there is no data to show? Or does it work some other way?

@danabra.mov Vid related: 1drv.ms/v/s!AljYTpCi...

I experience the same thing in the Android app. My feeling is that the tap detection is overly sensitive to the scrolling motion. Even the slightest amount of y-movement prevents the tap from registering.

If you ever decide to try it for your form component, I'd be very curious to hear how it went :)

Hi Hendra, I've been thinking about better form components a lot lately, so let me shamelessly plug my post: teletype.in/@smalldogene... - hope you'll find it helpful!

Let's say I want to implement a minimal framework with RSC support. Where do I even start? The Next.js codebase is frankly unapproachable as an example. Should I wait for the React 19 release and proper documentation?

Ah, good point that state updates cannot be instantaneous in async components. Yes, a separate tree of async components makes sense in this case.

Not strictly about RSC, but about async components. I heard that client async components were considered at some point, and there was even a prototype. Did it support stateful hooks? If so, how was this possible without async context? If not, would it have been possible with async context? :)