janka

(feeling vulnerable might delete later etc)

also just very destabilizing like. mentally. everything sucks

ugh us->eu jetlag is so upsetting

(although "static shell" is not quite accurate -- if it contains a cache, the shell will become ISR and will revalidate as often as needed to satisfy the specified staleTime)

the other important part is that in PPR + dynamicIO it serves as a marker that says "this can be part of the static shell" (if the staleTime is long enough), don't create a dynamic hole here". so it's kind of a lot of things in one

not sure wym by "something more official", but happy to answer questions

yeah the transform itself isn't that involved, in next we're repurposing most of the "use server" logic for it

cacheLife is important, one of the goals of this is to not just cache things server side but also inform the client-side router about how long stuff is allowed to be stale

ok balteus time! kinda tough but seems beatable if i get my execution together and capitalize on openings better

rn i'm playing it like the monster hunter of fighting robots, we'll see when i get to the dark souls part

she's purble

armored core is fun! i feel like i kinda suck at it rn but: big robot go pew pew whoosh slash slash

tbh the sheer amount of work hendrik has been doing recently makes the rest of the team like occasional weekend contributors

also iirc all witness testimony has to be in a form of Q&A right? so you basically *have* to do this if you want the jury to hear about something

rn i'm using a library that does some of the parsing but it's incomplete so i'm gonna have to roll my own probably

i'm making a tool to turn jsdoc into typescript because... because

parsing type annotations from jsdoc comments is a pain in the ass

nice! feel free to DM if you need any help with RSC internals or want to know how next.js does something with RSC

also i still have some ST keybinds ported to vscode bc i don't like changing my keyboard habits

yeah i was ride or die ST for a long time, vscode beat it on js tooling tho

i still use it for viewing big files (fast) and as my $GIT_EDITOR (vscode takes forever to open)

tbh i'm pretty sure i've bought one before, but i can't find it anywhere. it might've died with my old laptop :(

just bought a sublime text license, AMA

(and sublime merge, it's good)

you gotta hand it to billie eilish, she makes some salient points about lunch

reset the "days since" counter

i found out that the pope died from a "meets jd vance, dies of cringe" meme

if you wanna check the exact outputs, search the repo for "$$cache__" (we have a bunch of snapshot tests). but transform-wise it's basically just

$$cache__(...)

instead of

registerServerReference(...)

function outputs are serialized and stored as RSC payloads (of course). we run an isolated renderToReadableStream when creating a entry to minimize chances of cache poisoning. then the wrapper deserializes it back to have sth useful to render

it re-uses a lot of the server action transform (for hoisting/bound args purposes). then each cached func is wrapped with a wrapper that creates a cache key from the args, checks a cache for existing entries, saves some stuff into an ALS, etc

(i'm currently wrestling with a lot of cruft in the server actions impl so yeah i know sth about technical debt lol)

yeah it's gonna be so good when all the new stuff is finished

also generally one of the main points of 'use cache' is to be able to granularly know if we can skip sending something to the client (bc we know that what the client has is current/acceptably-stale)