the best part about writing is that i get to argue with people on the internet on the topics im interested in
added a little diagram at the end RE: View quoted note →
🙃 https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:fpruhuo22xkm5o7ttr2ktxdo&cid=bafkreig25u5dstlorfvxmlufffgnlwkppb7hdapl2rztrrc7cklpss44pe
so this is something i wanted to see movement on for a while and i’m pleased that it is happening. seems like a good opportunity to give feedback on related things; don't be shy RE:
generally the thing about this post is that like 90% of these features are either enabled or made much nicer by concurrent rendering. and the post doesn’t even say that because that’s just an implementation detail now. remember how uncool it was on the javascript pundit twitter RE: [React Labs: View Transitions, ...]( ) View quoted note →
idea for next overreacted post — taking each popular paradigm i'm familiar with (astro, htmx, remix, react query, graphql?) and turning it into rsc in a couple of steps. for the science. "many roads to rsc"
rsc is astro for react
that is, indeed, “the coolest shit” [youtu.be/-dePNpdd44M?...]( ) [React just got WAY cooler]( )
my theory with this post is that the concept of a "client reference" is not just an implementation detail or a technical term for advanced docs but a crucial part of building the mental model. i don’t know if my theory is correct yet RE: View quoted note →
i should say i don’t use ai in writing itself (not that i judge those who do but i don’t like the output) — but i do use it to kickstart the "filler" part of the code examples (like Express-like routes). these always stop me in the tracks completely because they’re so boring to write. now it’s fine