The Big "Server Waterfall Problem" with RSCs
Understanding server-side waterfalls with RSCs and client-side waterfalls we're familiar with and why server-side waterfalls are probably better.
Understanding server-side waterfalls with RSCs and client-side waterfalls we're familiar with and why server-side waterfalls are probably better.
React 19 introduces terrific primitives for building great forms. Let's dive deep on forms for the web with React.
React Server Components are going to improve the way we build web applications in a huge way... Once we nail the abstractions...
React components should not modify props directly. Learn why encapsulation is important and explore different approaches to handle props correctly in React, ensuring your components remain reusable and your application's data flow stays predictable.
Whether you're brand new to building dynamic web applications or you've been working with React for a long time, let's contextualize the most widely used UI framework in the world: React.
Forms can get slow pretty fast. Let's explore how state colocation can keep our React forms fast.
If you use a ref in your effect callback, shouldn't it be included in the dependencies? Why refs are a special exception to the rule!
Why can't React just magically know what to do without a key?
Excellent TypeScript definitions for your React forms
How to improve your custom hook APIs with a simple pattern.
Testing React.useEffect is much simpler than you think it is.
The sneaky, surreptitious bug that React saved us from by using closures.
How and why I import react using a namespace
How and why you should use CSS variables (custom properties) for theming instead of React context.
A basic introduction memoization and how React memoization features work.
Epic React is your learning spotlight so you can ship harder, better, faster, stronger.
Simplify and speed up your app development using React composition
Speed up your app's loading of code/data/assets with "render as you fetch" with and without React Suspense for Data Fetching
It wasn't a library. It was the way I was thinking about and defining state.
When was the last time you saw an error and had no idea what it meant (and therefore no idea what to do about it)? Today? Yeah, you're not alone... Let's talk about how to fix that.
Truly maintainable, flexible, simple, and reusable components require more thought than: "I need it to do this differently, so I'll accept a new prop for that". Seasoned React developers know this leads to nothing but pain and frustration for both the maintainer and user of the component.
Some common mistakes I see people make with useEffect and how to avoid them.
Is your app as fast as you think it is for your users?
I still remember when I first heard about React. It was January 2014. I was listening to a podcast. Pete Hunt and Jordan Walke were on talking about this framework they created at Facebook that with no support for two way data-binding, no built-in HTTP library, no dependency injection, and in place of templates it had this weird XML-like syntax for the UI. And to top it all off, I was listening to it while driving to the first ever ng-conf.