21–30 of 307 posts
This 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.
Seems like they have a bit more going on with progressive enhancement and interaction support, but nested routes are the headline for me.
Though as silly as it might sound, Remix’ publicity work has put me off it. Will read the docs anyway.
Nice. Defining multiple zones, each with their data and error boundaries, at little to no cost is a nice approach. Though as silly as it might sound, Remix’ publicity work has put me off it. Will read the docs anyway.
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 in an isolated way.
There's so much power this brings and the benefit is easily seen in how much less client side JS is really needed to build websites with support for lots of user interaction.
It's a push to go back to running code on the server that can, instead of shoveling everything into the client.
This is only the beginning of Remix, I'm excited to see what the team will bring.
If 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 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.
I'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…
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 more productive to me.
This looks neat but just like NextJS and Sapper it will not nicely play with my stack.
Earlier 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.
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.