Remix is starting to excite me

Поделиться
HTML-код
  • Опубликовано: 19 дек 2023
  • 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
    Ryan announcement tweet: / 1729274387671760936
    Remix roadmap on Github: github.com/orgs/remix-run/pro...
    Check out my Twitch, Twitter, Discord more at t3.gg
    S/O Ph4se0n3 for the awesome edit 🙏

Комментарии • 92

  • @markjohndalgleish

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

  • @user-xj5gz7ln3q

    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..

  • @anttihilja

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

  • @mattiarasulo9934

    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..

  • @MikeBifulco

    Remix's DX is great - I've enjoyed building with it, but completely abandoned it because the community (leadership) set a really strange tone, and butt heads with other dev communtiies in unproductive ways. That's enough to make me shy away.

  • @winstonyeo4342

    what about waku?

  • @gjhhj6y
    @gjhhj6y  +15

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

  • @MrStupiuno

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

  • @sahilaggarwal2004

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

  • @nonefvnfvnjnjnjevjenjvonej3384

    People should really look at PHP again. Frontend devs are such sheep.

  • @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!

  • @JEsterCW
    @JEsterCW  +75

    Remix DX over Next is like 10x more productivity without any shithole.

  • @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.

  • @shantanukulkarni007

    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.

  • @yarrichar

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

  • @seunghakim6748

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

  • @davidhollenbeck1674

    remix gang rise up

  • @kabal911
    @kabal911  +31

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

  • @OvidiuIspas

    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.