If you're like me, and have been building React SPAs for half a decade, Remix was much easier to pickup since 99% of what you already know (client components, React Router, Vite, etc...) is the same in Remix. The only new thing you have to learn is loaders and actions, which are way simpler than Next.js server actions and RSCs. More tutorials doesn't necessarily mean the framework is easier, it just means Vercel has deep pockets. That said, if you need SSG, ISG or really aggressive caching for a blog or public facing corporate site, Next does a better job at filling that niche.
Hey guys, I am new to remix and i was exploring a bit. I needed to add caching to my remix loaders responses on client side, but i am struggling to do that as i am facing so many bugs. Is there any resources that tell exactly how to do that?
Cool Video! I mostly agree with your points. The amount of resources is a very important thing. I almost stopped using remix because of the lack of resources on the web. Yet, after figuring some things out it is more enjoyable than NextJS for me. And then, if you somewhat know what you are doing, you don't need packages like next auth as you can implement it yourself. The fast dev server is also a big thing, makes the rapid development more rapid i guess. Also the loaders and actions are very smooth to work with in a structured way. And the Summary at the end is spot on at the time I write this comment. Currently sticking with remix, hoping it gets more resources :)
suppose it works for you perfectly. The react community is full of geeks who seek better solutions. However, to build stuff and make money it can be a waste of time to learn new fancy things if you aren't interested in them
