2d ago · 5 min read · Most teams pick React state libraries from npm trends or conference hype. Also in this series: Why React Error Boundaries Are Class Components: one of the few React APIs that still requires a class. That works until re-renders spike, boilerplate spr...
Join discussion
Apr 11 · 5 min read · Most teams pick React state libraries from npm trends or conference hype. Also in this series: Why React Error Boundaries Are Class Components: one of the few React APIs that still requires a class. That works until re-renders spike, boilerplate spr...
Join discussionApr 10 · 5 min read · Most teams pick React state libraries from npm trends or conference hype. Also in this series: Why React Error Boundaries Are Class Components: one of the few React APIs that still requires a class. That works until re-renders spike, boilerplate spr...
Join discussionApr 9 · 5 min read · Most teams pick React state libraries from npm trends or conference hype. Also in this series: Why React Error Boundaries Are Class Components: one of the few React APIs that still requires a class. That works until re-renders spike, boilerplate spr...
Join discussionMar 29 · 3 min read · I spent two years putting everything in Redux. Global loading states, form inputs, toast notifications — all in the store. Then I ripped it all out in a weekend and my codebase got 40% smaller. Here's why you should too. Redux was the right answer in...
Join discussion
