Remix is starting to excite me

I've...never been the biggest fan of Remix, let's be honest. That said, I'm really hyped about recent changes. With Mark Dalgeish pushing Vite and now Ryan Florence embracing React Server Components, the future is more exciting than ever

S/O Ph4se0n3 for the awesome edit 🙏

[markjohndalgleish]

Thanks for the huge shout out, it really means a lot to me 🙏

Just wanted to add that the Vite plugin was driven by Pedro Cattori just as much as me and it wouldn’t have happened without him 🍻

[VeitLehmann]

Server components never really clicked with me in the context of Next.js. I get the idea, I see the potential benefits. But with the Next.js implementation right now I don't feel like it's guiding towards a maintainable codebase. And the pages router in Next.js was also flawed. This concept is executed much better in Remix. So I'm really optimistic that the Remix folks will also find a great way of integrating server components. Yeah, I'm as hyped as you are!

[mattiarasulo]

I use Remix all day every day and it’s great as it is. If you need data in a component you can use a fetcher and use a resource route it’s untrue you are bound to only use route-level fetching..

[BobKane-gx]

Am I the only one who no longer finds any of these front-end frameworks exciting? Am I fatigued out? I watched Theo's entire video and all I can hear is blah blah blah.. blah..

[gjhhjy]

It’s dumb to dismiss route loading so heavily. It works, and is clear + productive.

[ThomasValadez-tv]

So... This route level data actually composes quiet well when working with nested layouts. It is an alternative solution to the problem mentioned of product detail component having it's own data.

[anttihilja]

Vite, single fetch, SPA mode, RSC, middleware, server context. Remix is getting loads of interesting improvements.

[MrStupiuno]

I thought you were a simple advert Vercel shill. This is a breath of fresh air tbh.

[hackerware_sh]

Good wrap-up video on Remix, however I believe the claim that loaders and actions are BAD DX is subjective. I have used both RSC in Next, and loaders and actions in Remix and actually love actions and loaders.

In my (subjective) opinion, the DX is actually like Tailwind: You may have mixed feelings when you see it from a distance, but wouldn't do it any other way once you used it!

[sahilaggarwal]

Theo is no longer my favourite vercel employee...?

[mintlata]

6:30 Where's the video in the corner about "SSR and how all of this stuff works"

[kabal]

The “lots of components that need data” pattern is the problem in react. People abstracting too many components.

in a ton of react projects I see, I'd say that 90% of the non-primitive components are used in 1 route, yet they are in some “shared” component tree

[shantanukulkarni]

And then "Everything fell apart". Last 15 years of js and Frontend development summed up in 3 words

[ShaneCodes]

I'm so pumped that you're getting into remix.

[beexactlyhereandnow]

finally I can hear about remix on this channel!! I have been really looking forward it! thanks!!

[ccccjjjjeeee]

i love remix's router, and i'm excited to see how they fit rsc into it. theres still issues, but ive been getting somewhat remix pilled too lately.

[yarrichar]

Thumbs up for the really clear explanation of server components, and the benefits. It hadn't really clicked for me before. Thanks!

[mentoriii]

i like DX more on Remix than Nextjs, also i like Remix embraces the good old web platform

[Adityacode]

Remix has a useMatches hook using which you can access data of any route in any component. So whats the problem with route level data fetching?

[magne]

5:40 Dai-shi just released Waku, which is exactly that.