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
![АЛАУДИНОВ у Скабеевой: эти их ВСУ нас НЕ ДОГОНЯТ 😁 [Пародия]](http://i.ytimg.com/vi/an0anqU4WGQ/mqdefault.jpg)
When you bet on Remix (soon RR7) - you bet on web standards, vite eco-system, etc. With NextJS you bet on Vercel.
betting on vercel that billing will be 5235235252$ monthly cuz most of ppl host apps there LUL
FACTS!!!
@@nikita-shtimenko I agree with this.
Death experience
So:
Nextjs for content-driven and/or static content
Remix for dynamic or data-driven content.
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.
Cool , i understand the difference now , i tried remix with a next background , and i found difficulties with the flat routing 😅
Yeah honestly I don’t really like flat routes
100%, When I saw this I said, what a hack, why? But I jump into v2, and there is folders, YEAH!
Remix route also works with folder and vite config. Framework is amazing!
Now yes, but when Jan recorded, I guess it was not.
Hey Jan, nice video there. Any plans to make more Remix video tutorials?
Remix for the Run!!!
remix is great, but there are not many resources in yt,I wish for some more complex and deep content about building remix app videos
subs: "de̶v̶s̶ death experience" 💀
Same thing, right?
Remix, Drizzle - top DX
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?
remix youtube official channel explained that and it is easy
Hey Marshal, your Ai-chatBot is not working, can you fix it.
Remix wins!
amazing vid
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 :)
Thanks for your comment! I definitively agree with you 😀
These are all but hypes, just used React in the frontend and Fastify in the backend.
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
Remix is superior.
Man can you be my code partner ?
I need to be with people that are a little bit above me 🙏🏼 please i will appreciate it
I can, am a senior web dev looking for a junior
@@omokaroelliot1942 hey lets connect
@@omokaroelliot1942 @kingjune6685 can i join you ?
I'm the only one seeing that he has a Aston martin cap and mclaren hoodie. That doesnt work man :D Choose a team
Pssssst 🤫 in my closet I also have Red Bull and Ferrari.
remix should pay you at this point
Yeah maybe I should send them my PayPal 😂