Remix – A framework focused on web fundamentals and modern UX
51–60 of 307 posts
Re: Remix – A framework focused on web fundamentals and modern UX
#52Earlier quoted context omitted.
> If you look at this example[0] you'll see there's not a single useState, useEffect, etc. Sorry to point it out, but there is useRef, useEffect and a useUserData on lines 48, 53, and 47 respectively.
Ah i missed those cause this is different from the demo they showed. But the point still stands. There’s not a useDtate per form field which is how react normally handles forms
Re: Remix – A framework focused on web fundamentals and modern UX
#53Re: Remix – A framework focused on web fundamentals and modern UX
#54I know this is low-value, but it always stuns me to see basic typos on a product’s landing page (lets —> let’s). Have the creators shown it to anyone else? Has nobody close to them told them about it? I don’t blame anyone for making a mistake - everyone does it, and I’m certainly no exception. But typos like this make a product feel much less professional and by extension less trustworthy. To me, good copy feels impo…
Re: Remix – A framework focused on web fundamentals and modern UX
#55I know this is low-value, but it always stuns me to see basic typos on a product’s landing page (lets —> let’s). Have the creators shown it to anyone else? Has nobody close to them told them about it? I don’t blame anyone for making a mistake - everyone does it, and I’m certainly no exception. But typos like this make a product feel much less professional and by extension less trustworthy. To me, good copy feels impo…
I kind of like the odd error here and there. Makes me feel safe to at least try out their product.
Re: Remix – A framework focused on web fundamentals and modern UX
#56Anyway I’ll give it a try on some side project, looks nice if you need something simple built fast (maybe with supabase or some of those new kids on the block)
Re: Remix – A framework focused on web fundamentals and modern UX
#57I really wish there were frameworks that developed ways to plug in with your already favorite backend kit instead of solely isometric with Node. You couldn't pay me to give up Phoenix in Elixir for backend work but it does lock off a healthy amount of the neat things being done to make data loading on the frontend more optimal. Phoenix has LiveView + AlpineJS but I really don't want to give up React which still feels…
Re: Remix – A framework focused on web fundamentals and modern UX
#58I really wish there were frameworks that developed ways to plug in with your already favorite backend kit instead of solely isometric with Node. You couldn't pay me to give up Phoenix in Elixir for backend work but it does lock off a healthy amount of the neat things being done to make data loading on the frontend more optimal. Phoenix has LiveView + AlpineJS but I really don't want to give up React which still feels…
It only technically is built for Rails and Laravel but reading the “spec” and the code I got it to work pretty quickly with a Rust backend.
It would be nice for more of these frontend niceties to be built around an API contract rather than a particular JS on the server implementation.
Re: Remix – A framework focused on web fundamentals and modern UX
#59Re: Remix – A framework focused on web fundamentals and modern UX
#60For sure next.js is an interesting framework and of course I use plenty of typescript in my projects to keep the UXs from feeling stale, but I have yet to see the overwhelming benefits that going all-in with something like this framework would give me overall, besides just the obvious one that I'm "keeping up with the cool kids"...
One think I do really like here is the way Remix is keeping things on the backend...I'll admit coming from the 1980s I'm much more comfortable working with backend paradigms, so this particular stack has caught my attention more than others and why I am particularly interested in hearing about its direct benefits (besides the obvious ones like "its not PHP" of course)