This article is stating the obvious about any software abstraction: Don't over generalize up front but look at commonly used patterns and create abstractions f

This article is stating the obvious about any software abstraction: Don't over generalize up front but look at commonly used patterns and create abstractions from there that fit many use cases. At the same time, there are common patterns that people expect to be there (a button component), and I'm always shocked when design system teams spend tons of money writing their own vs reusing other existing component libraries. On top of this all: component libraries need to take tons of non functional requirements into account nowadays (SSR compatibility, lazy loading data for paginated tables and how components interact with hybrid sever/client data loaders, offline caching of rendered components in service workers, etc), so not having some really good actual software engineers on the "design system team" can end in total disasters.