“Even if you haven’t accomplished the things you expected to at the start of this year, trust that setbacks and disruption are the norm rather than the exception, good times or bad, even on React.” –Rachel Nabors, Inside the React Core team
In this post from Stitch Fix Technology, Claire Niederberger and Matthew McMillion explain the motivation behind Stitch Fix’s move from monolith to microservices with the help of Rails and React.
This list of questions and thoughtful answers from Michael Sakhniuk is really outstanding. Read it prior to an interview, or better yet, just read it now!
Readers of the newsletter know that I love contrarian takes on technology. In this post, Jesse Luoto shares some of the problems with React, and his proposed alternative library, Longwood.
The React Core team released this talk in late December, and it’s worth watching. Dan and Lauren explain and demonstrate Server Components, a proposed feature that lets you render components on the server. Zero effect on bundle size, direct backend access, automatic client code splitting, opt-in adoption, and a modern UX with an old-school DX are some of the proposed benefits.
One of the early pitches for React was: “use as little or as much React as you need.” That’s still possible today! Sprinkle some React into your existing application, give it five minutes, and then evaluate.
Do you want to really (really!) learn React, while staying current on this exploding ecosystem? Subscribe to React Explained, a bi-weekly newsletter of amazing, curated React news and resources, simply explained. It’s free! Subscribe now.
Tweet
Share