Shadcn/UI now defaults to Base UI instead of Radix (ui.shadcn.com)

Article summary

Shadcn/UI now defaults to Base UI instead of Radix, with the option to still use Radix. The change is due to Base UI's stability and popularity among users. Shadcn/UI also introduced new components for chat interfaces and GitHub registries. The library allows for easy migration between Radix and Base UI using a skill for coding agents.

Main themes

• UI libraries
• Component migration
• GitHub registries
• Chat interfaces
• Coding agents
• Customization

What commenters say

• Using a UI library can be beneficial for rapid development, but it can also lead to a lack of customization and differentiation between applications.
• Some developers prefer to build their own UI libraries to have full control over the design and functionality.
• The use of coding agents and skills can simplify the migration process between different UI libraries and components.
• There is a trade-off between the convenience of using a pre-built UI library and the flexibility of building a custom solution.
• The complexity of modern front-end development makes it difficult to create and maintain a custom UI library.
• Some developers prefer a copy-paste approach to UI development, while others prefer to use lower-level abstractions and build components from scratch.
• The ability to customize and extend a UI library is crucial for creating a unique brand identity and user experience.
• The choice of UI library depends on the specific needs and goals of the project, and there is no one-size-fits-all solution.