Remix clone Hacker News

In the company I just left, I actually went through the process two or so months ago of migrating their Vercel deployment to AWS. I evaluated several options that are listed on the website and on GitHub, and we landed on using OpenNext via SST, it was a low-pain effort, especially given the CTO's desire to also migrate off of Next.js.

As other commenters have touched on - my understanding is the purpose of OpenNext is to package the output artifacts of a Next build in a way that can be deployed to a serverless environment, analogous to how Vercel does it. The supporting projects like SST and the other links in the repo are to take those OpenNext artifacts and deploy them to infrastructure generally in an opinionated way - additionally supporting some of the "extra" features described in the repository.

The last project I was working on was to then migrate from SST to Fargate, as a persistent process (serverful?) deployment was preferable for various reasons. In that scenario, we would just be running the built in server using the Next.js standalone deployment mode (effectively a `node index.js`). We didn't need the extra functionality covered by OpenNext.

▲

kcrwfrd_ 5 days ago | parent | next [-]

What’s the CTO’s motivation for migrating off of Next.js? And to what?

▲

mdhb 5 days ago | parent | next [-]

Next is actively a bad stack run by an incredibly shady company would be a good start

	▲	arez 4 days ago \| parent \| next [-]
		bad stack in what way? Why is vercel shady? I can understand that the business model is questionable to lock-in people with developing a framework that runs best on their own cloud, but shady would mean fot me, that they do something illegal
	▲	kcrwfrd_ 4 days ago \| parent \| prev [-]
		Could you substantiate that?

▲

greyskull 5 days ago | parent | prev [-]

Didn't get far enough along to understand the motivations and considered alternatives.

▲

pier25 5 days ago | parent | prev [-]

> especially given the CTO's desire to also migrate off of Next.js

To Remix?

	▲	0xblinq 2 days ago \| parent \| next [-]
		I think remix is a lot better. But the problem is that the team behind it (same as react router) have spent the last 10 years changing their mind every Tuesday and rewriting everything and breaking every API, it’s a cat and mouse game of chasing their latest idea all the time. Btw, remix itself is deprecated. There you go. What would I use? For sure I’d go with a MUCH saner and stable approach: inertia.js as the glue between React and a real full stack batteries included framework such as Adonis, Laravel or Rails.
	▲	greyskull 5 days ago \| parent \| prev [-]
		Didn't get far enough along to understand the motivations and considered alternatives.