imagining this app in a year… server rendered with RSCs… twice as performant thanks to React Compiler, and twice as fast again thanks to Static Hermes…
(of course, i’m not too serious, and i’m also not a web dev, and i do realise not everything would move to server side, but i do think there’s value in one api all apps share?)
i mean i guess it’s similar to inventing a new service, “app view view”, that talks html (or similar) and not atproto, but i guess the “problem” is that when you are running both the app view and the app view view, it’s unnecessary overhead to have the app view view actually talk to the app view
yep and in fact we were considering making such a service anyway (backend-for-frontend architecture). It’s actually way less overhead since if we run app logic in the rack right next to the appview it’s ultra low latency, we’re able to cut down waterfalls and give the client exactly what it needs
I think I've said it before but being able to open the network tab on here and see the actual http requests without everything being ssr is an underrated dx boost
I wonder if there's a halfway point between full SSR and retaining the generic 'atproto browser' function - like edge compute/cache with xrpc bulk-fetch endpoints (i.e. so you send your query/dependency tree and get back a bunch of state all at once)