Though provoking article @danabramov, thanks. I am wondering: What are the gains of RSC over a Fat Resource (with expand, sort, select and filter) where respon

Though provoking article @danabramov, thanks. I am wondering: What are the gains of RSC over a Fat Resource (with expand, sort, select and filter) where responses for (expand,sort,select) are cached? Most applications are READ-heavy, so even a fat response is easily returned to the client and might not need a refetch that often. The article briefly mentions that you need $expand and $select then, but why/when is that not a valid approach? The other point I have is that I really do not like to have JS on my server. If my business logic runs on a better runtime, we have 3 (actually 4) layers to pass: Storage layer (DB) -> business logic in C# (server) -> ViewModel layer in TS/JS (server) -> React in TS/JS (client). Managing changes gets really complex, with each layer needing type safety.