DEV Community

Discussion on: How is Remix different from Next.js

Collapse
 
nontechieguides profile image
Rich Cook

I'm trying to wrap my head around use case. I'm not a developer; just a guy trying to build better websites for my own businesses. I became an SSG fan after being frustrated with my WP site that was slow and got hacked despite my efforts. I discovered Jekyll then Gatsby and Next.

That as background, I've discovered all of this JavaScript based SSG/SSR, etc. builders and love them. I've grokked enough JS over the years to understand the basics and I see the huge potential for others like me who are frustrated with those monolithic builders.

But, until yesterday, I believed that SSGs were the best alternative. After reading a lot and watching a handful of YT videos, I'm seeing Remix as a possible better solution.

So, for a small business or maybe a nonprofit organization that needs more than an online brochure website, but not a full blown highly dynamic web app for the business ... is Remix an appropriate option? Or is Next the better way to go?

Remix, what I've seen after discovering it 24 hours ago, looks better because it seems to require less deep level JS ... e.g., the getStaticPaths in Next screwed me up; I struggled to connect it to my Sanity backend. Remix seems to handle this in a more direct ("simpler" is the right word but it's close) way.

Thoughts?

And thanks for the article. It was a big help in my understanding Remix.