A developer's attempt to update a simple radio button led to a deep dive into Shadcn and Radix UI components. What should have been a quick styling fix turned into an exploration of over 200 lines of code, multiple dependencies, and unnecessary complexity.

The author discovered that Shadcn's radio button implementation relies on Radix UI primitives and renders button elements with ARIA attributes instead of native HTML inputs. This approach contradicts web standards that recommend using built-in elements when possible, adding JavaScript overhead for basic functionality.

While component libraries aim to solve cross-browser styling issues, modern CSS provides straightforward solutions using `appearance: none` and pseudo-elements. The debate highlights a broader concern about dependency bloat in frontend development and the trade-offs between convenience and performance.

This discussion matters because small implementation choices compound across applications. Teams should evaluate whether pre-built components add genuine value or just extra weight. The simplicity of native HTML elements often gets overlooked in favor of complex tooling.