2 ms·
Unfortunately I will have to move a significant codebase out of Next.js to perhaps Remix as I run into all mentioned points.
by flagged24 3y ago
Unfortunately I will have to move a significant codebase out of Next.js to perhaps Remix as I run into all mentioned points.
- 0xblinq 3y ago> Unfortunately This is not unfortunate. I've done this recently and I'm so glad I did. Remix is much, much, much simpler and pragmatic. And doesn't have all these artificial limitations Next.js has when you're running it on your own server. I can't recommend it enough.
- flagged24 3y agoIt's unfortunate as this will take a lot of dev time from a well running project on the page router. Remix certainly looks good, I've done a small project with it and like how actions and loaders work. But it's also less polished and has a smaller community. For instance a relative simple thing as running Remix from a subfolder was overly complicated. There is also no guarantee Remix won't pull a 180 like Next.js did. The devs have a history of breaking changes with React Router.
- 0xblinq 3y agoYes, this is true for any js framework (and most libraries) to be honest. If you want something “safe”, nowadays the only option is to use one of the big MVC frameworks (django, laravel, rails, etc...) with inertia.js, if you want to use React or Vue.