Shadcn/UI now defaults to Base UI instead of Radix
21–30 of 180 posts
Re: Shadcn/UI now defaults to Base UI instead of Radix
#22That's great. Started using Base UI early on via 9ui [0] and found the primitives very pleasant to work with, especially if one wants to compose more complex components from other Base UI components. Maybe Shad can reduce some of the dependencies they rely on now. [0] https://www.9ui.dev
All of these component libraries look the same.
Re: Shadcn/UI now defaults to Base UI instead of Radix
#23Why? What advantage does it bring?
So essentially they look and operate the same as Radix components at the shadcn level but you have low-level control later on should you need it.
Re: Shadcn/UI now defaults to Base UI instead of Radix
#24What is the shadcn/ui equivalent for Angular? PrimeNG had a licensing change recently and I'm looking at a suitable alternatives for a fresh project.
Both attempts [1] to surface this on HN failed but if you are using a PrimeTek component library you need to be aware of this change.
PrimeNG, PrimeReact, and PrimeVue are all going fully closed source and ongoing licencing will be $800 per developer seat in 2027. [2]
The previous repos have been archived. [3]
PrimeFaces remains open source but it's now developed and maintained by independent volunteer developers who are not employees of PrimeTek.
[1]: https://hn.algolia.com/?q=The+Next+Chapter+of+PrimeTek
Re: Shadcn/UI now defaults to Base UI instead of Radix
#25For boring applications - do people prefer the copy paste approach of shadcn instead of a traditional ui library like mantine? The copy paste approach may be easily modifiable but creates new problems - ie now there is an upgrade ai agent for something that should just be ticking up a version number.
Re: Shadcn/UI now defaults to Base UI instead of Radix
#26Why? What advantage does it bring?
Base UI is more low-level, a lot less opinionated and doesn’t force you into certain layouts. This of course makes it more complex to use, but that doesn’t matter if you’re using shadcn components because they’re doing that work for you. So essentially they look and operate the same as Radix components at the shadcn level but you have low-level control later on should you need it.
Re: Shadcn/UI now defaults to Base UI instead of Radix
#27What is the shadcn/ui equivalent for Angular? PrimeNG had a licensing change recently and I'm looking at a suitable alternatives for a fresh project.
Re: Shadcn/UI now defaults to Base UI instead of Radix
#28For boring applications - do people prefer the copy paste approach of shadcn instead of a traditional ui library like mantine? The copy paste approach may be easily modifiable but creates new problems - ie now there is an upgrade ai agent for something that should just be ticking up a version number.
Re: Shadcn/UI now defaults to Base UI instead of Radix
#29Why? What advantage does it bring?
Re: Shadcn/UI now defaults to Base UI instead of Radix
#30Tangential but does anyone an have opinion on Base UI vs React Aria? Trying to decide between the two atm.
Having a library not in anyway related to that to me feels like a big pro.
I have found React Aria to be very good. I really like how its a set of hooks, a set of premade components using said hooks, and I like how you can choose bits of either approach for your own components. Some of the hooks are very useful.