A @lambert.fun is an amazing asset.

I've only seen people do this using one of the myriad `react-server-dom-` packages... github.com/facebook/rea...

Will that produce RSC? Looks like it produces a stream of HTML?

Thanks!

I’m speaking from ignorance on that and would love if that’s true! Gotta adopt it on our code and see!

It depends on the expense of those renders whereas selectors tend to be drastically cheaper. I think Redux’s useExternalSyncStore and hooks implementations are good evidence of that.

In our case, a single context update without granularity could mean tens of thousands of renders. And if those renders are higher order components their reconciliation cost is multiplied... Sounds like the team is going to stick with the compiler bailouts in render rather than granular context read?

I wish you could see the sorts of things we've had to do to squeeze performance out of React at Webflow. Granted we're running a web app within a web app... but many of our unit tests leverage counting to ensure that optimizations aren't broken over time.

Really excited about compiler for us.

Would really love to get granular updates from context updates. I remember seeing the idea of memoizing within use calls?

Hey thanks for sharing!

By the time I'm done on this planet it'll all be archives of shame... 😆