This seems interesting but the rendering bugs on the website don’t give me much confidence.
Remix – A framework focused on web fundamentals and modern UX
41–50 of 307 posts
Re: Remix – A framework focused on web fundamentals and modern UX
#42I see no mention of Typescript support. Anyone know?
The create npx command has a typescript option, the entire framework seems to be typed nicely, the demo was all typescript. I’d be surprised if they didn’t write the whole thing in it.
Re: Remix – A framework focused on web fundamentals and modern UX
#43How can this be integrated with react-query and react-location? Seems that it's tightly coupled to their variants (SWR and react-router). React Query is IMO a must-have on any project that already warrants using React (and that isn't an offline-only app of course).
I think the goal here is to avoid needing something like react query. The loader functions you write execute on the server and pull data that is needed by the component.
You can of course still use react query/swr/redux tool kit etc if you want. Remix doesn't limit what you can do and still fully supports any of these and other client side tools.
Remix just encourages to make better use of server side code instead of shoveling everything into the client.
Re: Remix – A framework focused on web fundamentals and modern UX
#44I 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…
We're in the same boat. Wouldn't give up Phoenix on the backend for anything. We are gradually adopting LiveView with great support for components. Have you tried it?
Agree Remix looks good though!
Re: Remix – A framework focused on web fundamentals and modern UX
#45Earlier quoted context omitted.
They just did a demo with a simple form and looking at it seemed so obvious. There was no useState per form element, form data was trivially validated on the server, errors were trivially sent down to the server. If you look at this example[0] you'll see there's not a single useState, useEffect, etc. Fundamentally, Remix is about using native browser behavior to build websites. The imported `Form` component is replac…
> 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
#46Made me think of Ethereum's remix, an amazing IDE all-in experience to write smart contracts: https://remix.ethereum.org/
Re: Remix – A framework focused on web fundamentals and modern UX
#47Earlier quoted context omitted.
They just did (maybe still going) Q&A session where they did a demo and answered question. Remix seems to be more like PHP or Ruby On Rails, it handles both server side functionality (calls to db, third-party APIs...) as well as the frontend code in a single file.
That can be done on NextJS as well using getInitialProps, getServerSideProps, or getStaticProps Some of the notable differences between NextJS and Remix are the following: - While both support file-based routing, Remix is baked with React Router -- giving developers the capability to declare custom routes without sticking to file structure conventions - NextJS banks on its static site generation to generate "cache-ab…
It doesn't really promote its use, but it's exceedingly easy to use cache headers with Next.js if you're using getInitialProps or getServerSideProps.
My issue with Next.js (alongside lack of nested routes) is that it has a handful of weird light abstractions which make things marginally easier for developers for the most common cases, but completely tie the hands of people who know what they're doing. To that end, Remix is a little more appealing.
Re: Remix – A framework focused on web fundamentals and modern UX
#48Earlier quoted context omitted.
Remix might be a few years too late to be honest. After watching the session, there does not appear to be any significant differences from Next.
the team behind remix probably has the biggest following in the react scene, so even without having any major differentiation (though I happen to think they do have) it's going to gain popularity.
I'm sure outside of my personal bubble this won't be an issue, but I've found the buzz generated from this announcement to be kind of off-putting. The sheer amount of promotion leading up to this announcement has been in my face now for weeks and kind of driving me nuts.
That being said I see no reason to not welcome another competitor in this space... and it's free. I'm sure you are right and this will gain popularity, though the competition is stiff.
Re: Remix – A framework focused on web fundamentals and modern UX
#49Earlier quoted context omitted.
They just did (maybe still going) Q&A session where they did a demo and answered question. Remix seems to be more like PHP or Ruby On Rails, it handles both server side functionality (calls to db, third-party APIs...) as well as the frontend code in a single file.
Next.js has an /api folder that does that, is it similar?
Their form demo is definitely worth checking out. You could build the same thing with a Next API route. You’d need to write some code to do the validation that they do, but it should largely look something like their hook does. Hopefully Next will build something like it because this is a much more sane way to write forms than the controlled inputs and state way.
I do think it’s nice having it in the same file as the form itself, but it’s not clear how well that’ll scale in a more complex page with many forms. So I think Next could get most of the way there with a few helpers to make a form submit to an API route with similar DX.
Re: Remix – A framework focused on web fundamentals and modern UX
#50I 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 important enough to be a top priority, at least on your landing page…
If a friend shared their new site with me and I saw a typo like this one, I would flag it to them every time.