It’s getting tiring to hear at this point, but the Claude voice comes through clearly in this post, and it’s a little off-putting. If even an important product release doesn’t warrant full human attention, where will we draw the line?
show comments
chvid
For 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.
show comments
notnullorvoid
It bothers me that these popular UI toolkits render copious amounts of divs. I went to look at Base UI and for nearly every component it's "Renders a <div> element", when there are native elements that can achieve the same thing like details/summary for accordion.
I'm far from a native web evangelist, I think there's a lot the web APIs especially HTML gets wrong, but div overuse is also wrong.
gherkinnn
I have used and mostly like Shadcn, and yet their Radix-based radio button was a bit much, as are other choices, where similarly overblown solutions were used.
That'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.
It’s getting tiring to hear at this point, but the Claude voice comes through clearly in this post, and it’s a little off-putting. If even an important product release doesn’t warrant full human attention, where will we draw the line?
For 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.
It bothers me that these popular UI toolkits render copious amounts of divs. I went to look at Base UI and for nearly every component it's "Renders a <div> element", when there are native elements that can achieve the same thing like details/summary for accordion.
I'm far from a native web evangelist, I think there's a lot the web APIs especially HTML gets wrong, but div overuse is also wrong.
I have used and mostly like Shadcn, and yet their Radix-based radio button was a bit much, as are other choices, where similarly overblown solutions were used.
https://news.ycombinator.com/item?id=46688971
Moving away from codemods and towards LLMs doing migration work is an interesting development.
Even if they’re more deterministic, I wonder if the days of codemods are numbered.
url should be https://ui.shadcn.com/docs/changelog/2026-07-base-ui-default
I'm still on Daisyui and feeling FOMO here. Is it worth the switch and why?
What 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.
On React Native support: https://github.com/mui/base-ui/issues/2612
Shadcn is great until you want to use it
I miss a good old skeuomorphic styleguide. I guess the last one was Blueprint?
My choice is https://www.skeleton.dev/
That'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
Why? What advantage does it bring?
This reads like a script to a Theo video
Curious if anyone tried Astryx that was open sourced by Meta last week to see how it compares.
Tangential but does anyone an have opinion on Base UI vs React Aria?
Trying to decide between the two atm.
Most of the websites I found are still on the radix version.
Imagine building a brand new component library to replace your already quite successful component library and still making it React-only.
based