just wanted to note that the react docs says that you shouldn't use server functions for fetching data (last bullet point): react.dev/reference/rs...

you also probably need something like react query to do polling and fetch data for your infinite scrolling data tables (since no implementation of RSC have a great answer for these problems yet?), and then it's just easier to only go with react query

the same goes for refetch when something changes, you don't want to refetch the screens that have not changed. nextjs parallel routes is a cool solution to this problem, but I don't think it's very well known

in practice a lot of screens in advanced web apps are actually composed of multiple independent screens. which screens should be shown in this larger screen is also dependent on some combination of backend and client state. so trying to fetch everything at once becomes both slow and very complex

www.youtube.com/watch?v=FYvi...
some poor woman is just trying to get some work done while a bored looking dude comes crashing down behind her