Started a project in Next.js and it quickly felt bloated and inconvenient. After 15 days, I gave Remix a try, loved it, and recoded the project in Remix. It's been 3 months of uninterrupted coding now, best decision ever. Now I'm moving away from Vercel as well...
@johanan_offl19 күн бұрын
Remix + Cloudflare Stack = W
@ruaidhrilumsden Жыл бұрын
I don't think Remix will ruin everything when they get round to using server components. The people behind Remix are so much more interested in keeping aligned with web standards and I can't see them introducing RSC until they're totally happy that it will be a positive experience for everyone - users and developers. This means making everything predictable and introducing instinctive abstractions.
@mistymornings3 ай бұрын
100% agree.
@tzuilee588 Жыл бұрын
Remix seems to be a little bit more stable than nextjs app router
@ZombiEquinox Жыл бұрын
I've been using Remix for close to a year now. It does have a learning curve to it but it's pretty great. I am excited to see the community growing.
@dorinelrushi0 Жыл бұрын
Remix is a great asset for production-ready projects
@aaronmendez9284 Жыл бұрын
Wow Cody, finally great to see you joining the Remix gang now :) We've been waiting for you..
@oreip_ Жыл бұрын
Those features of loaders, actions, and the Form component in Remix are things that I have used with just react router dom. Looks like I'm going to learn Remix since I'm already used to using those things.
@WebDevCody Жыл бұрын
yeah Remix is built on top of react router, so the transition is easy
@martinemanuel823911 ай бұрын
I've been a longtime user of Next.js in my projects, but after giving Remix a try, I find it remarkably easy to use and is super intuitively. Transitioning from react-router was even smoother, making the switch quite seamless. I totally agree with this review
@youneshenni5417 Жыл бұрын
Unfortunately, the developer experience does not always correlate with market demands. And from what I see, the market share for react and next is still strong comapred to these lesser-known frameworks.
@wongtungtung7456 Жыл бұрын
But why?
@nickolaki Жыл бұрын
@@wongtungtung7456 Because its backed by Vercel and Vercel is massive.
@74Bagas Жыл бұрын
naturally. still developer experience is the key though. but yeah, it's javascript world 😂. and it's good to see, like web dev cody with remix, james q quick with astro, etc. even bun vs deno, let's see.
@DEV_XO Жыл бұрын
🥳 Remix is simply great! The developer experience is unmatched!
@zeronl_abs9 сағат бұрын
Next js dev server made me burnout when i changed to remix i found that i started enjoying coding again
@ilijanl Жыл бұрын
When hosting remix on vercel you can set the s-maxage cache control headers in the loader function to get the CDN SWR cache behaviour (which is similar to ISR)
@WebDevCody Жыл бұрын
oh, very nice
@ilijanl Жыл бұрын
@@WebDevCody a good article to read is nextjs Vs remix on remix's blog which discusses several cache strategies
@ugentu11 ай бұрын
Oh, I felt I was the only one who had that crash! Also, I found that components often got messed up CSS\SCSS when rendered on a server. Classes hierarchy breaks, and highest classes attributes might be overridden by base classes. Server-to-Client mismatch errors are quite a pain in the ass as well. It's really hard to debug when it's only happening on production... In the end, you need to enforce\simulate common components behavior quite a lot. Almost any tension to state management, handled navigation, or user behavioral tracking with experimentation will hit a sell of SSG\ISG capabilities, and you need to fallback to SSR\CSR. And Remix's approach really seems like something I'm trying to milk from Next. The routing is based on React Router 6, and that's really handy and well-supported by libs. While updating to every next NEXT(sorry) version takes much longer time for a considerations..
@BeeBeeEight Жыл бұрын
I've used remix for a project before and it was really cool. If you've used react router then you'll find it much easier to understand the routing in remix since remix also created react router lol. Another nice little thing about remix is they even recreated the error boundary as a functional component so we don't have to touch the default class component like in next js.
@henriquematias198610 ай бұрын
"they will ruin everything with server components" haha that's how it feels with Next a lot of the time, just a lot of extra complexity on top of something that was already working like a charm !
@xbsidesx Жыл бұрын
What is the vscode theme you’re using? Thank you!
@manuelestebanmoraleszuarez43607 ай бұрын
I wonder the same
@eshw23 Жыл бұрын
Is Next 13 really that bad? Ive been building my saas for the last 6 weeks with the app router and overall its great, yea the slow dev server and the experimental stuff can be annoying, but overall its 100x better than using plain react and figuring out how to do the same complex stuff with Express and then claw my brains out trying to figure out how to deploy it Thanks.
@WebDevCody Жыл бұрын
I mean, I’ve never had a Ui framework constantly crash on me saying out of memory and take seconds to reload simple changes at times. Are you using server actions, or do you just use RSC and revalidatePath & refresh when data updates?
@eshw23 Жыл бұрын
@@WebDevCody I use server actions and router.refresh when data updates yes. In development my site is slow, but the deployed version is blazing fast.
@ugentu11 ай бұрын
It fells bad when your static-vs-dynamic data vision is different from Vercel's vision. And for sure it's better than pure react. So thins transition from React to Next and then to something more suitable for your domain - seems natural.
@odairsilva106 ай бұрын
The Dev Experience is smoothier with Remix. While coding you know Remix is there but it still feels like a pure create-react-app experience.
@AlexM86 Жыл бұрын
What is your opinion on svelte/sveltekit? I've seen some code a few days ago and I've been diving into it and loving it so far. I would personally love to see a video of you bringing your thoughts of svelte, either as a newcomer or an experienced dev
@WebDevCody Жыл бұрын
I've used it once before, I like it but the idea of single file components turns me away
@FarleyTheCoder11 ай бұрын
How do you feel about it now? I'm thinking about changing after 3 years of solid nextjs.
@user-ew5hp6ug7v3 ай бұрын
Can you please explain what is the 'Value', in the Deploy & Run Transactions Tab? Why is it zero? What happens if you increase the number? How does that affect the token once it gets deployed? Thank you in advance for your help.
@davidentzat5671 Жыл бұрын
Thanks for sharing your thoughts.... it will be great if you post more videos related to Remix.
@tevoj Жыл бұрын
The thing that I really don't like about nextjs is the cache system. It works until it doesn't. Things that I just don't want to worry until I really need to.
@WebDevCody Жыл бұрын
Exactly, caching should always be opt in.
@3b00d09 Жыл бұрын
Do you recommend devs that are newer to react but not to web dev learn next’s page router rather than app router?
@WebDevCody Жыл бұрын
I think the app router is ok, but I wouldn't use any experimental / beta features unless you're just playing around.
@eshw23 Жыл бұрын
@@WebDevCody What do you mean expirmental/beta features? Do you mean not have the final production level app with the App router?
@WebDevCody Жыл бұрын
@@eshw23 I mean server actions are experimental
@onorlidmedina Жыл бұрын
Thanks for all your content, what do you think of astro?
@WebDevCody Жыл бұрын
Astro is nice as well, I personally just don’t like the difference between coding in an Astro specific syntax vs dropping down into react / vue. Astro feels like I’m using two different libraries just to build a dynamic application. But for a static multi page app I’d pick astro due to how small the output files are
@siya.abc123 Жыл бұрын
Hey man this is yet another video. What helped me with the Next dev server crashes was to use node lts. I was running on Node 20+ and I my server kept crashing. Node 18.17.1 seems to work fine. But dev server is still slow
@WebDevCody Жыл бұрын
I'm currently on node 18x. Someone mentioned it's related to react-icons causes next to run out of memory... but I'm not sure at this point and I don't have the time to debug
@ugentu11 ай бұрын
For me it start crashing when moved from 16 to 18
@TedMosby-fk5gj Жыл бұрын
Outside of your work and saas, how do you improve as a dev? Do you play around with these different frameworks? Is that how?
@WebDevCody Жыл бұрын
Yeah just play around with various things, watch other KZbinrs report stuff they’ve been learning or playing around with, experiment on things at work sometimes
@imkeyi2 ай бұрын
Solid explain!
@benmcmullan7188 ай бұрын
I'm trying to get into react from using jquery for like 5 years with Laravel SSR. I'm building an SPA for a RESTAPI backend on Laravel. I need dynamic routing, should I use react and react router or something like Remix or Nextjs?
@TheSuperBoyProject2 ай бұрын
Whatever you end up choosing make sure it has SSR. Many benefits but mainly for the better SEO.
@justin.johnson2 ай бұрын
Remix IS React Router Use Remix, Tailwind, Drizzle ORM and enjoy your life Cheers 🥂
@BakriHmouda Жыл бұрын
I highly recommend that u give sveltekit a shot
@MrBlack-dz2le11 ай бұрын
what is this amazing font in vscode?
@GameOfflineIsLove6 ай бұрын
How do i add loading on server side in remix? , in next js, i can create a file call loading.tsx
@rodrigorb2630 Жыл бұрын
React-query is not needed in remix, due to the way it handles revalidation
@WebDevCody Жыл бұрын
I’m using a backend as a service which updates data live as it changes via websockets
@jagadeeshgade63099 ай бұрын
Can you upload a video of using any ui framework like react bootstrap in remix
@adimardev1550 Жыл бұрын
that "use client" stuff is a total breaker. a framework that keep changing unreasonably, is no good framework. i'd been using next for more than 3 years and kept up with its changes. i loved it, i build an ecosystem of stacks with it. and now, it totally breaks it. because application is built not just by a framework. but with the ecosystem of technologies working together. and next14 just breaks it and we have to rethink again. i'd been keeping up with its changes but i think not this time. as of my research, I'm hyped about qwik city, solid start and astro.
@raprincis10 ай бұрын
Remix is simple and awesome
@mikah1308 Жыл бұрын
Same experience where I kept having to restart the npm run dev and it takes so long to compile the page
@alexjohnson-bassworship3150 Жыл бұрын
Atta boy!!
@appel-32 Жыл бұрын
Im literally getting the same errors as you, i freaked out the first time that i ran out of memory. Im getting issues with redirecting too, and the cache is giving me headaches
@WebDevCody Жыл бұрын
I’ll check back in a few months when maybe they fix their framework
@ronikikoza Жыл бұрын
Hi, which vscode the you are using?
@WebDevCody Жыл бұрын
bearded theme
@avi7278 Жыл бұрын
I used to have that dev server memory crash on next all the time, it was super annoying and then I set some config option in next config, (I'll have to look at which one) and it totally disappeared, and so did the problem with (literally) 30 second page loads on the dev server.
@avi7278 Жыл бұрын
It was this, drop this in your next config object (root) and love life again: experimental: { esmExternals: false, },
@cybetheus8 ай бұрын
I think u r saviour
@alharethturab7612 Жыл бұрын
These are the same reasons why I've been using qwik more than react(next) recently
@twitchizle11 ай бұрын
You dont need loader to get the params
@griffadev Жыл бұрын
Probably the docs fault but seems like your example where you had a button on click using useNavigate should probably just use the Link component?
@WebDevCody Жыл бұрын
I’d need to check my code, but I think I create a database record first then I navigate to the room
@griffadev Жыл бұрын
@@WebDevCody sounds like might be a good place to experiment with an action potentially. We recently did a Hackathon day learning remix at work and getting lost in the docs was a common issue feel the pain!
@idavidgeo10 ай бұрын
App Router was a mistake. This is at least how me and some of my colleagues think. We'll be sticking to the pages dir for a while now. It's been working like a charm.
@martiananomaly9 ай бұрын
Except the app router is better in every way
@idavidgeo9 ай бұрын
If that’s your experience, more power to you. I like my code without layers of abstraction.
@pheisar Жыл бұрын
I'm having so many issues with everything related to caching in next 13, it's soooo frustrating. Non intuitive behavior regarding the useRouter API, client cache not having any optout at all. I find myself having to reach for useEffect and window.location API, which completely defeats the purpose of using next 13 at all. How did we end up in a situation in which the mainstream react framework is a mess? 😫😫
@brokula1312 Жыл бұрын
Try Nuxt3
@WebDevCody Жыл бұрын
I have, I like nuxt
@paulmarolop11 ай бұрын
what is that vscode theme ?
@WebDevCody11 ай бұрын
Bearded theme stained blue
@paulmarolop11 ай бұрын
thanks a lot@@WebDevCody
@Gaash.shmilovich Жыл бұрын
what is this amazing theme?
@WebDevCody Жыл бұрын
bearded theme
@nickwoodward819 Жыл бұрын
what are the docs like? react router docs are pretty... uh, 'messy'. it's definitely put me off remix a little
@dopetag8 ай бұрын
The more I get into trouble with Next.js the more I want to try Remix. I hope it is not worse... These meta-frameworks are not mature enough
@ashimov197011 ай бұрын
so you have completely abandoned Next/React for Remix, right?
@WebDevCody11 ай бұрын
nope, I decided to stick to next
@ashimov197011 ай бұрын
@@WebDevCody why so?
@AbdelrahmanMoussaAbuOuf7 ай бұрын
Why?
@manumene16 күн бұрын
when asking to open AI keep on mind version v1.5 and 2.14 are different
@tabdig Жыл бұрын
Remix seems more stable, but for my brain very confusing. I will just contuine with next.js 😅
@o_glethorpe Жыл бұрын
How did you grow a beard so fast lol
@WebDevCody Жыл бұрын
I eat my mini wheats
@alasassi5889 Жыл бұрын
I heard that salary of web-developers will decline by 70% because of AI is that true ? And what we should about it?
@WebDevCody Жыл бұрын
maybe one day, but AI keeps giving me bad answers, so the AI should be paying me more to fix their issues
@emmanuelezeagwula7436 Жыл бұрын
I call cap on that one
@justin.johnson2 ай бұрын
Hahaha some of you are starting to see the light. I ditched next years ago for everything Remix. Don't follow trends of bloated annoying frameworks. And FYI dude Remix is React Router and why the docs reference it so don't complain about them not wanting to write duplicate documentation. Welcome to Remix, the BEST developer experience which results in better software for users. Sincerely, Senior Full-stack Software Engineer
@achaabni8 ай бұрын
I agree Next is never stable, you have something working and a little upgrade and then boom a lot of functionality doesn't work
@ChrisOkw9 ай бұрын
remix has server components now as well
@manumene16 күн бұрын
Remix is easier to understand
@laptopuser5198 Жыл бұрын
The docs used to be better, then they switched to the "re export of react router"
@WebDevCody Жыл бұрын
yeah I'm not very impressed with the docs, they seem very all over the place
@ember2081 Жыл бұрын
Looking great, though "V2_MetaFunction" is ugly as all hell