Very well written (as expected) argument for RSC. It's interesting to see the parallels with Inertia.js.
(a bit sad to see all the commenters that clearly haven't read the article though)
I was immediately thinking of inertia.js.
Inertia is "dumb" in that a component can't request data, but must rely on that the API knows which data it needs.
RSC is "smarter", but also to it's detriment in my opinion. I have yet to see a "clean" Next project using RSC. Developers end up confused about which components should be what (and that some can be both), and "use client" becomes a crutch of sorts, making the projects messy.
Ultimately I think most projects would be better off with Inertia's (BFF) model, because of its simplicity.
inertia is the 'pragmatic' way. your controller endpoints in your backend - just pass the right amount of data to your inertia view.
& every interaction is server driven.