Remix 3 is a continuation of the Remix framework that abandons React and is more experimental. The old remix did indeed "work itself out of a job" by simplifying all of its features down until it became version 7 of the react-router library
IMO it's an amazing story. Remix was once a paid framework that focused on "using the platform". Then they open sourced it. Then they realized all of their work could be reduced to some new features of the popular react-router library.
They're basically the exact opposite of Nextjs which has a reputation of advertising framework features that are actually more like Vercel features. Though I acknowledge nextjs has been making a lot of progress on reducing their "soft lock-in"
On your last point, could you elaborate? I have been using Next.js for a long time and I have never once interacted with Vercel. What soft lock-in are you referring to? I often deploy it using OpenNext and SST in AWS.
Curious to how much is just good marketing on their side and how much is maybe features of it I don’t know that are “vercel native”
If you are using OpenNext and SST (or Netlify), then you are doing it right. Most people assume you can just throw a Nextjs project into a docker container and don't realize that there are many features that don't just work "out of the box". The entire OpenNext project exists because of this massive gap
The reason I called it "soft" lock-in is because all of the nextjs features are technically self-hostable but often require extra setup that is sometimes completely undocumented. Until recently, Vercel itself didn't even use the default build outputs. It had an undocumented flag that skipped some serving logic that was handled by the Vercel platform itself.
Dax Raad from SST actually did an interview going more in depth into some of the features that don't exactly work "out of the box" as advertised (PPR, ISR, image optimization). This interview is about a year old and luckily Vercel has been collaborating with OpenNext to resolve a lot of these concerns but its still ridiculous that these were ever issues to begin with
For anyone else confused:
Remix 3 is a continuation of the Remix framework that abandons React and is more experimental. The old remix did indeed "work itself out of a job" by simplifying all of its features down until it became version 7 of the react-router library
IMO it's an amazing story. Remix was once a paid framework that focused on "using the platform". Then they open sourced it. Then they realized all of their work could be reduced to some new features of the popular react-router library.
They're basically the exact opposite of Nextjs which has a reputation of advertising framework features that are actually more like Vercel features. Though I acknowledge nextjs has been making a lot of progress on reducing their "soft lock-in"
On your last point, could you elaborate? I have been using Next.js for a long time and I have never once interacted with Vercel. What soft lock-in are you referring to? I often deploy it using OpenNext and SST in AWS.
Curious to how much is just good marketing on their side and how much is maybe features of it I don’t know that are “vercel native”
If you are using OpenNext and SST (or Netlify), then you are doing it right. Most people assume you can just throw a Nextjs project into a docker container and don't realize that there are many features that don't just work "out of the box". The entire OpenNext project exists because of this massive gap
The reason I called it "soft" lock-in is because all of the nextjs features are technically self-hostable but often require extra setup that is sometimes completely undocumented. Until recently, Vercel itself didn't even use the default build outputs. It had an undocumented flag that skipped some serving logic that was handled by the Vercel platform itself.
Dax Raad from SST actually did an interview going more in depth into some of the features that don't exactly work "out of the box" as advertised (PPR, ISR, image optimization). This interview is about a year old and luckily Vercel has been collaborating with OpenNext to resolve a lot of these concerns but its still ridiculous that these were ever issues to begin with
https://www.youtube.com/watch?v=E-w0R-leDMc