oh this is cool, didn’t realize this RE:
svelte is considering implementing concurrent rendering in the future! https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:fpruhuo22xkm5o7ttr2ktxdo&cid=bafkreidbsy2gadsbei2wniv45osonn7z6s4bdhs43a3cdmth3bezdz3wra
enshittification sounds like something from a red hot chili peppers song
super excited about more frameworks treating asynchronous rendering as a first-class feature. this strikes a different set of tradeoffs than the ones chosen by React but there’s also quite a bit of convergence. RE:
my blog analytics is showing exactly three visits from instagram. i wonder what the story is there
ryan gets it RE:
the fact that console logs are now transferred by Next.js to the browser with a [Server] badge in devtools is wild. i thought it would be weird from the PRs but now i'm trying it and it feels so good
hot take, you should call your endpoints get_users_v1 and such to remember it’s ok to iterate in backwards-incompatible ways when you also maintain the clients (or if don’t mind running multiple versions for some time)
is it just me or is something interesting happening here? an interactive SortableList component re-renders on the client in response to state changes, but its rows are described by PostPreview which does a readFile(). but it composes perfectly fine. i find this fascinating, is it not to most devs? https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:fpruhuo22xkm5o7ttr2ktxdo&cid=bafkreidabkb7rmu5hxnqfqbqlphr3wo6pyw3x3wz2oob5vmhbhopjl2eca
okay should i write this https://morel.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:fpruhuo22xkm5o7ttr2ktxdo&cid=bafkreih6cgrmmvqknwsokgurb3aut35ezawhcqukwwijhylmzuvvq3vrae