Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any plans for better Radix or ShadCN like support? #30816

Open
dreamstar-enterprises opened this issue Apr 6, 2025 · 0 comments
Open

Any plans for better Radix or ShadCN like support? #30816

dreamstar-enterprises opened this issue Apr 6, 2025 · 0 comments
Labels
feature This issue represents a new feature or feature request rather than a bug or bug fix needs triage This issue needs to be triaged by the team

Comments

@dreamstar-enterprises
Copy link

dreamstar-enterprises commented Apr 6, 2025

Feature Description

This is the big elephant in the room, that Angular needs to (with urgency!) catch up on, despite the faster signals performance. Here is what A.I. says repeatedly about the component and styling system in Angular (this is not me, but a popular LLM's opinion):

React has a much richer ecosystem of polished, accessible UI component libraries:

  • Radix UI provides unstyled, accessible primitives with excellent composition patterns
  • Shadcn/UI offers beautiful, customizable components built on Radix primitives
  • Headless UI, Chakra UI, Material UI, and many others provide different approaches to component design

Angular's component library options are more limited and often less polished:

  • Angular Material is the official library but can feel dated and inflexible
  • PrimeNG and NG-Bootstrap exist but don't match the developer experience of modern React libraries
  • Many Angular libraries feel more heavyweight and less customizable

The Tradeoff

This creates a genuine tradeoff for developers:

Angular: Better performance architecture with signals, but weaker component ecosystem

React: More comprehensive and modern component libraries, but less efficient rendering approachReact's Component Library Advantage React has a much richer ecosystem of polished, accessible UI component libraries: Radix UI provides unstyled, accessible primitives with excellent composition patterns Shadcn/UI offers beautiful, customizable components built on Radix primitives Headless UI, Chakra UI, Material UI, and many others provide different approaches to component design

Angular's component library options are more limited and often less polished: Angular Material is the official library but can feel dated and inflexible PrimeNG and NG-Bootstrap exist but don't match the developer experience of modern React libraries Many Angular libraries feel more heavyweight and less customizable

The Tradeoff This creates a genuine tradeoff for developers: Angular: Better performance architecture with signals, but weaker component ecosystem React: More comprehensive and modern component libraries, but less efficient rendering approach

Use Case

No response

@dreamstar-enterprises dreamstar-enterprises added feature This issue represents a new feature or feature request rather than a bug or bug fix needs triage This issue needs to be triaged by the team labels Apr 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature This issue represents a new feature or feature request rather than a bug or bug fix needs triage This issue needs to be triaged by the team
Projects
None yet
Development

No branches or pull requests

1 participant