@ryanflorence It’s one thing to diplomatically congratulate a new president — any president.
But to specifically call out the fragmented media landscape and channels of misinformation, red-pilling and radicalization that fostered this outcome is despicable. Disqualifying.
@ryanflorence Thanks for clarifying. I’d be stoked for a Reverb/Remix v4 that re-founds itself on top of React 19. That could really bring back the Remix v1 simplicity and excitement (which got lost in all the RR back-and-forth and Vite transition). Bit of a branding limbo until then, though.
@ryanflorence Oh man, yeah — please don’t. I realize that Remix must ride the RSC hype train to future-proof itself and stay relevant. But a lot of the appeal and simplicity of Remix is in danger of being flushed out with the bathwater. Thanks for taking your time with this!
I created my #FirstPullRequest 12 years ago, also the first PR to this repo. Glorious XSLT days! Classic unsolicited PR that never landed, but A+ feedback from A+ human (and developer) @greystate 🫶
https://t.co/8RhAnKIvFE
https://t.co/YvDUKxO3rn
@ryanflorence Much better! There was also something in the docs at some point that for the longest time made me think that fetchers didn’t have the same non-JS fallback as Form, thus making me avoid them 🙃
@perborgen@scrimba Would love it! I teach modern full stack (JS, React, Remix, Mongo etc) at a BA programme in Web Development in Aarhus, Denmark:
https://t.co/hMpWPzGmzl
@chancethedev@remix_run Noooo! What a huge loss for the ecosystem and, I can only imagine, for the team. As seen from the outside, you’ve been a really defining part of the Remix “vibe” — friendly, helpful, thorough and pedagogical. You’ll be missed. But congrats to your new team on picking all that up!
@ebey_jacob@elonmusk Psst, @chancethedev is on Mastodon, why don’t you come over too? The water is nice. Maybe we can even resurrect the ghost of Ryan and get a whole Remix thing going over there 😉
@brophdawg11@mjackson This is a really great approach. Looking forward to following a hopefully stable and successful v2 release 🤘
@brophdawg11 That final “docs” link is a 404 btw.
@ryanflorence@rauchg So now we have a third option to add to @mjackson’s wget-powered solution (https://t.co/6KpXA36ilW) and @ebey_jacob’s cache-loaders-as-json-files solution (https://t.co/pYAh6DETUS). Can you guys coordinate and ship something soon? 😄
@jimniels@remix_run A big loss! Your graphics and explainy blog posts both on your personal site and the Remix blog were really good — I’ve used them when teaching my students on several occasions. Looking forward to seeing that skill be put to good use elsewhere.
@ryanflorence Yeah, that’d be great. If you’re using TS it’s easy enough to “introspect” the available props, but for JS developers it is currently not very discoverable.
The docs are very approachable for newcomers, but less optimized for regular users that quickly need to look something up.
@ryanflorence I like how the React Router docs include a collapsed type declaration, which is useful (although it requires some TS literacy). Clearly that is easiest for maintainability. E.g. compare the Link docs for Remix with RR:
https://t.co/0Ue7HHZRUf
https://t.co/r4fnD6da3m
@ryanflorence Mostly, but sort of hidden within the prose. And I love the conversational, approachable tone of the docs. But it would be great to pair it with a quick-reference overview of the props, like e.g. the React Native docs: https://t.co/zywG3gDdm0 (under "Reference").