Software engineering is about tradeoffs. Let's talk about how data fetching happens in different meta-frameworks and what the trade-offs of those approaches are.

That looks familiar! I proposed pretty much exactly this API in a Remix RFC a while back. The trade-off from our perspective is that it requires even more compiler magic and makes normal refactors more likely to break correctness.

Yes this is solved with the code extraction magic of $().

Well, you can technically do multi loader patter with RSC by exporting data function that starts promise and inside the component you just use it with React.use

Yes as I said there are ways around it. But I am more interested what is available out of the box.

Great vid Misko! Man, data is confusing!

this is great! i'd love one about mutations with loader revalidation

Vue is also going for the multi-loader approach. But we have to write keys but you don't why? I know this is a minor inconvenience but SSR mechanics make devs do too much work!

Could you point me to some docs / code examples? We don't because of $() 1. creates the keys automatically for you and 2. allows you to directly refer to server code without pulling it into the client

I love the video though wish you would have used the same example of artist and playlist so it's a 1-1 example

Thanks for the feedback. That is a fair point.