I prefer using Next. I've been using Remix at the day-job for about a year now. It's fine, but I still choose to use Next with all personal work. I'd also prefer to work with it professionally. My personal dev-blog started in v12, I upgraded it to v13 a while back (not much involved in that upgrade), and at this moment am refactoring it to v14. A lot has changed, and for the better.
It provides a great solution for most needs and problems. But I think the biggest selling point is that their docs are excellent. I never connected with the Remix docs...they often left me still confused. I've used Remix v1 and updated our two work repos to v2. I still don't feel fluent with it for some reason and often find myself thinking "I prefer the way Next does this".
Someone else here mentioned the T3 stack. That's a good resource to at least see other libraries/services that work well with Next. You don't need to follow any of it blindly, but use it as an information resource.
Comments
I prefer using Next. I've been using Remix at the day-job for about a year now. It's fine, but I still choose to use Next with all personal work. I'd also prefer to work with it professionally. My personal dev-blog started in v12, I upgraded it to v13 a while back (not much involved in that upgrade), and at this moment am refactoring it to v14. A lot has changed, and for the better.
It provides a great solution for most needs and problems. But I think the biggest selling point is that their docs are excellent. I never connected with the Remix docs...they often left me still confused. I've used Remix v1 and updated our two work repos to v2. I still don't feel fluent with it for some reason and often find myself thinking "I prefer the way Next does this".
Someone else here mentioned the T3 stack. That's a good resource to at least see other libraries/services that work well with Next. You don't need to follow any of it blindly, but use it as an information resource.