Cursor/Windsurf's "pair programming with the AI" approach is far better.

Yes, you cannot generate an entire project in mere minutes this way, but it's still VERY fast, and you have human eyes on the code developing a real understanding for all the moving parts.

All told, it's been a year and a half of hard work to get to today. We've got so much to share about this project. Let us know what you'd like to hear about! :)

youtu.be/0mCsluv5FXA

my ego is going to get so big if Claudr keeps telling me "brilliant insight" for every nontrivial observation

unfortunately the state-of-the-art LLMs are at least as, if not more, terrible at answering questions about CSS. which clearly implies that CSS is actually harder than all the Phd level questions they do so well at

(specifically, RSCs are highly amenable specifically to high-fidelity networks, as they strongly connect the client and server instead of placing an architectural cutpoint there)

and correctness here is very much a matter of not just opinion, but probably even philosophy. so it's not so much wrong or broken as a way to solve the problem that doesn't jive with how i and probably some others believe the web should work

well, i put those two terms in quotation marks for a reason. they are certainly technically impressive, but the key is that it's a solution that is much more available to the react team to do by themselves while staying within what react is today. from their position it's a very sensible thing to do

relevant @ryansolid.bsky.social stream for this (the entire thing is well worth watching)

which would be okay if the client-side suspense cache was anywhere close to completion but there is no visible progress on it