Stop Adding React Components Just Because You “Like” Them

Short summary

A frontend engineering piece arguing against creating React components purely for syntactic preference when native HTML already handles semantics. The core principle: abstract behavior, not syntax. A Heading component that just renders an h3 adds maintenance cost without value, while a Text component that centralizes design tokens and truncation is a legitimate abstraction. The author advocates for one concept, one API, and composition over abstraction.

• •Don't abstract syntax — abstract behavior
• •Every new component adds documentation, testing, and maintenance costs
• •Prefer composition: use native HTML for semantics and Text components for design tokens

Generated with AI, which can make mistakes.