We really should be able to wholly skip winters during Times Like These™.

Yeah, sorry, the character limit precluded me from linking directly 😅

When I first saw it in the docs, I thought they were asking it to *be* the linter, which would be quite non-deterministic and wasteful. The spell-checking can be defended, I guess, but definitely ressource-intensive.

This is in the official Claude Code docs 🤷‍♂️

"lint:claude": "claude -p 'you are a linter. please look at the changes vs. main and report any issues related to typos. report the filename and line number on one line, and a description of the issue on the second line. do not return any other text.'"

That’s great! And you’re sure it’s not mostly because Next has been busy shooting itself in the foot during that year? 😜

Perfect, thanks! Freaked me out that it was editable until I spotted the embedded JSON in the URL 😅

Very useful visualization. I enthusiastically embraced Remix v1 in my teaching when it came out (and RR7 now, natch), so if I end up adopting Remix 3 I’ll be sure to steal this 😄

That’s a fair point. And I really hope it does. Looking forward to playing with it.

And I get the attachment to the name and branding, but it really should’ve had a new name to signify the new path. This makes it hella hard to google anything (and confusing for LLMs, the main audience?) 😅

Yeah, I know the existing upgrade path and have been through it. And RR7 has all the functionality of Remix intact (massive props to you guys on the team). We just lost all the excitement and enthusiasm along the way, which is really sad. There was so much buzz thrown out with the bathwater.

Bluesky seems to be scaling this to an unreadable resolution (at least on iOS) 😬 Any chance you have a hi-res version you can link to? Looks very useful, and I really want to understand it.

But this will be doubly true for Remix 3, won’t it? No more React, an entirely new set of primitives, no upgrade path at all — despite what the name might suggest? Your diagram pretty clearly paints it as its own island. It’ll be a hard sell, regardless of its merits — unfortunately.

This is so wonderfully nerdy, I love it. I too wrote XSLT in my first developer job (Umbraco websites ~15 years ago) and I absolutely loved it, and still miss it.

I’m perpetually wanting to build an XSLT-based static site generator (which I know that nobody but myself would ever use). #xslt4lyfe

Very enlightening as always. Thanks.

But also a lot of words (once more) to make up for the fact that React Server Components should have been named better 🫠