Content
@
https://opensea.io/collection/dev-21
0 reply
0 recast
2 reactions
Chris Zhu
@czhu12
Spent friday night learning Remix, and ended up with reframe.canine.sh Basically Retool for your own life. See the one i made for myself at reframe.canine.sh/czhu12 Mostly happy with it, I set it as my default new tab link, and it's a good way to kickstart my brain.
1 reply
3 recasts
16 reactions
jtgi
@jtgi
current takes on remix?
2 replies
0 recast
3 reactions
Chris Zhu
@czhu12
`const data = useLoaderData<typeof loader>()` is pretty magical. Not having 10 lines of useState to start every component is awesome All web frameworks are kinda moving in this direction. Rails has turbo frames which is pretty similar.
2 replies
0 recast
7 reactions
Hoot 🎩
@owl
I’m seeing some complaints about the weird merge with react-router, bad docs and then tending to break a lot of core functionality with new versions. Haven’t used it long enough to confirm any of those but so far after understanding the core principles I like it as a more native feeling alternative to next
2 replies
0 recast
2 reactions
jtgi
@jtgi
I’m waiting a bit for react router 7 switchover to mature. I wish they kept the name remix but tbf they’re the most conscious team I’ve seen about backward compatibility (see their flags) and remix was already just reexporting out of react router for the last year or so. Agree feels more native than next. Less files. No lambdas. Deploy it anywhere. Still react. I am still jealous of Rails though.
1 reply
0 recast
1 reaction
Hoot 🎩
@owl
Briefly used early remix in the past and now started with react-router version from the get go. Surprisingly the API is almost exactly the same so you can just read the old docs or tutorials, change the imports and you’re good. One annoying thing though is that vercel doesn’t have native deployments yet so you have to configure some express server stuff to get it running
2 replies
0 recast
2 reactions
