2 ms·
Aside from replacing Remix with Next.js, this is also what I would recommend. Remix makes things that were simple hard (apparently with the goal of doing _ever
by Aeolun 4y ago
Aside from replacing Remix with Next.js, this is also what I would recommend.
Remix makes things that were simple hard (apparently with the goal of doing _everything_ on the server again).
- bcjordan 4y agocreate-t3-app is a great starting point for folks going this path. Has optional checkboxes for db/ORM/migrations (prisma.js), auth/sessions (next-auth.js), tailwind CSS, typed client/server communication (trpc). https://create.t3.gg/ https://create.t3.gg/ https://github.com/t3-oss/create-t3-app https://github.com/t3-oss/create-t3-app I hadn't touched much webdev for a few years, the ecosystem / build tooling has gotten a LOT better. It's back to being fun and painless to spin up a new webapp.
- zulvkr 4y agoA few hours ago, I tried to setup trpc using recommended boilerplate, I also tried fresh default T3 after that. Both got error, which seems to be due to next/next auth dependency breaking. So it's not that painless I guess.. I found this situation quite often with nextjs example template T3 author is very responsive though, so my issue resolved quickly
- eagsalazar2 4y agoI can speak to a handful of things Remix needs to improve, but "makes things that were simple hard" is a very big generalization. Remix nets out for me big time. I've never been as productive with another framework. Also, remix does SSR but so do a lot of frameworks, is that what you mean when you say "__everything__ on the server again"??