> - You don't need integration with something like Storybook or Workspaces to develop and test components in isolation. You never needed this. Those things are

> - You don't need integration with something like Storybook or Workspaces to develop and test components in isolation. You never needed this. Those things are pure bloat. If you're building React components... build a static CRA app out of those components. Voila, you have real-world React examples, no Storybook garbage creeping in, no 3minute compile times just to find you didn't configure their stupid webpack setup to actually catch your TS errors, just the literal environment you'll use them in perfectly ready to go Otherwise, I don't strongly disagree, I think that this point is the real key to all these non-framework libraries though: > - You don't have the expertise/willingness/requirements to implement advanced and/or bespoke interactive UI features AKA your UI is KISS. (Like the ones mentioned in the article.) I can promise you people like optimistic app behavior when you write it well. And that's not possible with backend rendering.