Remix vs. Next.js
remix.run
Remix vs. Next.js
1–10 of 17 posts
Re: Remix vs. Next.js
#2I’ve been pretty deep into next js for a while. I’m excited to give Remix a try.
Very big fan of fly.io as well, they’re smart folks and I run every service I can on them.
Re: Remix vs. Next.js
#3The "pros" for nextjs seem believable, a non-bias piece /s
Re: Remix vs. Next.js
#4remix talks about too much simplification. Too much simplification scares me.
Re: Remix vs. Next.js
#5remix talks about too much simplification. Too much simplification scares me.
I agree. Part of what my team likes about next is that although it doesn’t get everything perfect, it’s generally close enough and otherwise often within the realm of customization when it counts.
The only exception might be the router. I’ve found it a little limited at times and there’s no way around it. This is one of remix’s apparent strengths, but it’s insanely comprehensive. I wonder if it might be too much in the other direction.
Re: Remix vs. Next.js
#6remix talks about too much simplification. Too much simplification scares me.
I agree. Part of what my team likes about next is that although it doesn’t get everything perfect, it’s generally close enough and otherwise often within the realm of customization when it counts. The only exception might be the router. I’ve found it a little limited at times and there’s no way around it. This is one of remix’s apparent strengths, but it’s insanely comprehensive. I wonder if it might be too much in t…
I spent a weekend playing around with Remix, and it didn't fail to deliver. I don't think you have anything to worry about.
Re: Remix vs. Next.js
#7Glad to see someone not focused on frontend.
Frontends are incredibly bloated already and next.js embedding react in any page is a killer for static websites.
Re: Remix vs. Next.js
#8Haven't heard of Remix, will give it a try. One thing that bugs me with Next.js is the missing data mutations part that Remix claims to address. When I setup my next.js project and was fetching data via getServerSideProps I was impressed. Until I realised there is zero support for mutating data. As soon as I need a single POST/PUT request, next.js support ends and you are back to writing your own fetch() code. It somewhat felt as if developers ended their day there, as you would definitely expect something that allows you to send data from the client to the server.
Re: Remix vs. Next.js
#9I started to use Remix and I love it, the nested routes / layouts is the most powerful feature for me. Also, the API is easier and cleaner than Next and the hooks to consume the data is a nice approach as well.
Re: Remix vs. Next.js
#10remix talks about too much simplification. Too much simplification scares me.
Simplification in this case means, it gets out of your way. The API surface is incredibly small. You have actually more flexibility than you do in Next.js with its proprietary methods.