there’s a bunch of good stuff in there. “hosted web, posted web and signed web” is another banger. RE:
i know RSC-in-browser doesn’t have great perf compared to real RSC but i think it’s compelling to be able to write a pure SPA using the same model RE:
more exciting post than usual. feels like every update precisely targets a current pain point. very encouraging RE:
the fact that this is possible is such a cool atproto demo. how many people complained about twitter search — imagine if it was possible for third parties to just build an alternative one. not the same magnitude here ofc but it’s cool anyone can build a search for any atproto app RE:
think having claude know, use, and suggest approaches like this when fixing problems would make vibecoding a lot more compelling. i’m sure it can get there with a bunch of prompting but this needs to be knowledge available to it out of the RE: View quoted note →
i wrote about how to fix any bug [How to Fix Any Bug — overreact...]( )
trying to teach claude to root cause bugs by removing things
this is the way to learn with ai. you can start anywhere and backfill. you have to remain curious and careful and not just passively eat up plausible explanations. but if you put in the effort and the model is good, it’s powerful RE:
this looks like it'll be a banger release [nextjs.org/blog/next-16...]( ) [Next.js 16 (beta)]( )
at the crossroads: currently i have a fully client-side SPA written with React Router 6. i like that i can deploy it for free anywhere however i do want stuff like OG images, ideally SSR for SEO, and i'd like low-latency access to data layer feeling tempted to port to Next