Since the dawn of time, React maintainers have claimed that React’s virtual DOM is fast enough for complex interactions as long as you memoized your components. Then someone tried to put an entire Harry Potter novel in React ProseMirror, and I had to find out if they were right.
React ProseMirror can really be quite fast, but what happens if we need to render it multiple times? Let’s walk through how to use React’s Transition APIs to speed up perceived performance by ensuring that only the critical interactive elements are updated immediately following user input.
Most teams treat technical debt as inevitable maintenance rather than strategic investment—but this approach fails because not all debt is created equal. Let's break down a framework for evaluating tech debt decisions with the same rigor as feature development.
There’s something off about the most popular approach to quieting React’s warnings about using layout effects during server-side rendering. Let’s break down why the warning exists, and when it really makes sense to disable it without actually addressing it.
For the past year and a half, I’ve been re-writing the renderer for ProseMirror, the popular rich text editing library. This new renderer has finally been marked as stable and published as part of @handlewithcare/react-prosemirror, a library that integrates React and ProseMirror. Here’s a very deep dive into the journey I took, and why it led me where it did!