Remix is a NEW JavaScript framework you MUST try

Remix is a new react-based JavaScript framework that supports server-side rendering. It comes from the team behind React Router and provides a fresh take on fullstack web app development.

#react #js #firstlook

🔗 Resources

📚 Chapters

00:00 What is Remix?
01:12 Server-side Rendering
02:01 Get Started
02:48 Routing
04:20 Data Fetching
05:01 Form Actions
06:19 Styles
06:54 React Server Components?
07:41 Business Model
8:08 Other Exciting Developments

🔥 Get More Content - Upgrade to PRO

Use code lORhwXd2 for 25% off your first payment.

🎨 My Editor Settings

- Atom One Dark
- vscode-icons
- Fira Code Font

🔖 Topics Covered

- What is Remix?
- React Remix Tutorial
- Does remix use server components?
- React Remix Basics for webdev
- Nested routing in remix
- How remix actions work

[MrTomro]

Legend says there's not a single day without a new JS framework being born.

[tnypxl]

I love how JS frameworks have come full circle back to server-side rendering.

[idrizpelaj]

It's great that web development is going back to its roots again with SSR.

[alexanderhemming]

this channel is likely one of the largest influencers of the development of the net now. Clearly the best resource for information gathering from the development perspective.

There is nothing else as concise informative and inspired.

Its a bit like John Oliver was for silly injustices

[neoncut]

Great video!

I loved the part where you talked about the types of apps Remix could be most useful for. Showed me the kind of thinking that goes into deciding how to construct the architecture of an app from the ground up.

I would love to hear you speak more about fundamental things like modern app architecture, toolchains, programming patterns or JavaScript best practices.

Your work is highly appreciated. 💚

[dninja]

"hiring people with 7 years of Remix experience"

[SidTheGreat]

Jeff: "The last thing we need is another JS framework".
Also Jeff: "Remix is a NEW JS framework you MUST try"

[CliffordFajardo]

Excellent video 🔥Some things that folks might not learn from the video (critical when deciding tech though)
1. Remix - Incremental Static Site Generation
- You can do this in Remix, setup your cache headers `state-while-revalidate` which is a browser standard.
- is it over kill for static content? I don't think so, it just doesn't come out of the box, but you get to learn and use the platform which is nice IMO; small lines of code

2. Remix - Static Builds
- You can achieve similar behavior by taking advantage of browser cache headers; once the page is built the first time, cache it for YOUR_DESIRED_TIME
- if you're really want this; use Puppeteer/Playwright to build your page at build time (cache headers is simpler)

My Summary
- Both frameworks are excellente, I prefer Remix for a few reasons:
- there is only 1 abstraction around data fetching in Remix (useLoader) vs 4 in NextJS (get{Static, ServerAide, Initial}Props) & client fetching
- I prefer Remix's "simpler" API / mental model (try it if you don't believe me 😉)
- there's a lot of other nuances, is Remix better than Next NO. Both frameworks have tradeoffs, I just really really like the tradeoffs Remix has made. Worth noting is that all these frameworks influence each other, so they each are getting better

[apidas]

8:37 this is why I switch to backend development. frontend guys are just crazy fixing unimportant problems with all the resources and just creating fragmentation among the solutions

[jamesknippel]

Jeff you almost have a million subscribers holy crap man

[LeCrowTV]

"But it might be overkill if your just building a blog that you post to once a year"
I feel personally attacked

[daleryanaldover]

I tried JavaScript frameworks but it did not really click to me, coming from Rails and Laravel environment it is much easier for me to work with server side logic. Thank you for sharing Remix, I might get my hands wet this weekend.

Also client side validation is really just an option, since remix focuses on the server side it is intuitive to do validation on the server side as well.

[TheNewton]

Now we need meta frameworks to help evaluate them so we can figure out what framework to use for a project.

[abdurrahmanfadhil]

"It's a lot easier to lose money and get acquired versus trying to sell a JavaScript framework."
— Jeff

[malachibergman]

Can we just appreciate the people that devote their lives to making us other developers lives easier. Personally, more than just the code, I’m so glad to be in a career path where people go out of their way to make a huge difference in the experience of literally thousands if not millions of people with what they write. It goes unappreciated, so if you’re one of those and you know who you are, thank you.

[coolsai]

Time goes faster than normal while watching your videos :)

[CodeWithSahand]

Consider how those who paid for it must be feeling now that it is available for free.

[MiguelFelipeCalo]

If you think about it, each react project are it's own framework, because more often than not, each react project is different in terms of libraries used.

[dcngn_]

I love the way you casually said the rainbow animation tricked your brain into thinking it must be good. I personally care a lot for aesthetics so I do get influenced a lot by the way a product is marketed visually. That's why I'm so torn when it comes to latex or vim. I rather use good looking editors like vscode with plugins instead of the more robust OGs

[sanjivgautam]

I still believe NextJS is still the best. Now the latest version also has a rust compiler underneath, so I am definitely not leaving NextJS for some time now.