Something new here? Because this is not new and gets posted semi-regularly every few months for a few years
Remix – A framework focused on web fundamentals and modern UX
31–40 of 307 posts
Re: Remix – A framework focused on web fundamentals and modern UX
#32Something new here? Because this is not new and gets posted semi-regularly every few months for a few years
Perhaps it was the v1 announcement that got it across your radar
posted a few hours ago:
Re: Remix – A framework focused on web fundamentals and modern UX
#33I see no mention of Typescript support. Anyone know?
It supports typescript completely
Re: Remix – A framework focused on web fundamentals and modern UX
#34I see no mention of Typescript support. Anyone know?
seems like the code in the docs [0] is typescript
Re: Remix – A framework focused on web fundamentals and modern UX
#35This website is impressive somehow, but also crazy to parse. Always at least two things going on at same time, the viewers' attention constantly split instead of being guided.
I found it incredibly annoying to read/parse personally. Huge fonts, stuttering animations interrupting my scrolling, and way too many colour/formatting changes to be able to smoothly read it. It's all very distracting and over-designed.
Re: Remix – A framework focused on web fundamentals and modern UX
#36How 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).
Re: Remix – A framework focused on web fundamentals and modern UX
#37I 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've done some "fat app servers" that consume GraphQL APIs. You could build a Phoenix + Absinthe app, then consume it from something like Remix.
The real problem is switching languages. I sure get slow when I change from Elixir to JavaScript. There's not a bright line between backend/frontend in a fullstack app, so I've been much happier minimizing how often I have to switch languages.
Re: Remix – A framework focused on web fundamentals and modern UX
#38I'm already so impressed by Remix after watching the demo today. Looking forward to Kent Dodd's demo tomorrow and to play around with the framework. It has a great balance between client and server code. Just as React brought the mental model of writing integrated HTML/CSS/JS for an isolated component, Remix seems to bring the mental model of writing client and server code that are associated to one another together…
Where can I see the demo?
Here it is! https://youtu.be/wsJaUjd1rUo?t=299
Re: Remix – A framework focused on web fundamentals and modern UX
#39If this is just Next.js with nested routes, it‘s already worth it. Seems like they have a bit more going on with progressive enhancement and interaction support, but nested routes are the headline for me.
I like to think of like this: I use Next.js for my marketing site. I use Remix for my web app. Next is good if you just need to get some HTML on the page. Remix is good if you need a connect to a database or backend API.
We can call it the Gatsby-Next-Remix continuum.
Re: Remix – A framework focused on web fundamentals and modern UX
#40I've been hearing about Remix since they were sponsorware, but I don't really get the appeal. They don't seem to show how it's different from e.g. Next.js, especially version 12 which seems to have a similar feature set of server-side plus static rendering, as well as React server components, and then a separate /api folder for any backend apis you want to set up.
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.