Historically we've seen that you can get fancy with state management solutions in React. However, the best solutions are often the most simple. In this post, Kent brings us back to the basics and convincingly describes why the solutions to our problems were the fundamentals all along.
If you’re anything like Zach, at least 3 or 4 of the keywords in the title of this article fall under the category of “things he's been wanting to play with but haven’t gotten around to it yet.” In this article, he does just that documenting his experience with each.
React Hooks promise to avoid the overhead of class components while delivering all the same benefits. For example, they allow us to write stateful functional components without having to worry about storing state on the class instance. However, writing stateful components with Hooks requires care. There’s a subtle difference between how state is initialized in the constructor of a class component and how it is initialized by the useState hook. This article dives into what that difference is and what you'll need to do to avoid (in certain cases) making your app slower than necessary.
Is Concurrent Mode just a workaround for “virtual DOM diffing” overhead? Some people got that impression. In this Twitter thread Dan clarifies and breaks down what benefits Concurrent React will give to your app.