3 ms·
> I would say if you know that you are going to use Vercel, use Next.js but otherwise I would always argue for Remix. Exactly. It makes absolute no sense to de
by 0xblinq 3y ago
> I would say if you know that you are going to use Vercel, use Next.js but otherwise I would always argue for Remix.
Exactly. It makes absolute no sense to deal with all of Next's artificially imposed limitations if you're running it on your own servers.
- ervine 3y agoWhat limitations? You mean like not being able to use the full node API in your middleware that's being run by the node server that you control in your own infrastructure? And how about that dev rel... no response since August of last year. https://github.com/vercel/next.js/discussions/46722 https://github.com/vercel/next.js/discussions/46722
- 0xblinq 3y agoThis is done so that you never use it (even in your own servers) because otherwise you won’t be able to move to their cloud. This is why you don’t use VC backed dependencies that are not easy to move away from.