shadcn/ui

“Obviously if your base is just unmodified shadcn, then it will look like any other toy site out there.”

“Start from an existing template or a component library with sane defaults (Material UI, shadcn, Tailwind UI - pick one and commit)”

“It is a component library which arguably could've existed without Tailwind ever existing.”

“React components like ShadCN and others is proof enough that Tailwind is a platform with the best pro/con ratio”

“Tailwind and ShadCN gets me there, my most backend-y backend engineer gets tailwind.”

“When you import shadcn components you can rebuild them however you want, thats the point.”

“you have to provide all the styles, rather than just overrides, which can be both a blessing and a curse.”

“I think shadCN has its place for sure but I'd always advocate for Mantine”

“because the code is yours its expected that you change the internal logic/styling/structure of the component”

“You own the code, not the library, hence you can fix whatever you need instead of relying on them to fix it.”

“To me, that's the value of shadcn (conceptually) - it's nothing more than a tool to bootstrap your own UI library.”

“upgrades are now easy; we can upgrade a single component -- add the new ones free.”

“Shadcn just reeks of a fad, and even after doing copy paste and trying it, I didn't see what the big deal was.”

“If you don't need to make any changes, it should be very simple to just upgrade by replacing the components.”

“I have used and mostly like Shadcn, and yet their Radix-based radio button was a bit much”

“it is still an amazing design system and also allows a ton of customization”

“The DX of SCNUI is already very good and LLMs are all too familiar with it”

“I used to use material UI for every project I made, but then I saw ShadCN/ui and immediately switched.”

“The design is shadcn – which is an MIT license - very very popular design system.”

“people were complaining about every startup website using the same basic format and shadcn for years”

“anchoring around a design system like shadcn is just way easier for a team to align around”

“a project using shadcn/ui is nearly immediately identifiable as such because most do not deviate from the defaults”

“it lets you do a lot of customization so you don't need to reinvent the wheels”

“LLMs tend to do better with component libraries like shadcn or daisy than writing raw CSS in my experience.”

“PWA dudes that all want to use some variant of shadcn or whatever same but different flavor of what is effectively the same design language”

“pairing an LLM with shadcn/ui gets me to a decent, responsive UI much faster than I would on my own”

“It collects several useful components, makes them consistently styles (and customizable), and is easy to add to your project”

“I've seen so many shadcn based scam sites that my brain starts associating shadcn with scams.”

“The library has in essence became an interface for developers to build for.”

“building a comprehensive open-source UI toolkit, on your own basically, isn't as easy as one would think”

“Shadcn gives you more freedom to fix stuff like this and rewrite how you want the component to work and look”

“What I do like about Shadcn, is that its components are yours to modify.”

“the fact that it just wraps another dependency (Radix) kind of defeats the purpose for me”

“I can simply pull free components (or components from another kit) directly via shadcn.”

“Radix/Shadcn (which uses tailwind for styling of course) that killed the need to buy Tailwind's UI kits”

“shadcn lives inside your codebase and you can fully customize it as you please”

“shadcn ui is not a component library but the basis for a component library that has great accessibility built-in from the start”

“competition from other template systems like shadcn that are completely free”

“It is much faster to just use some kind of component library, like shadcn, and let the developer figure it out.”

“it removes a lot of the mental load of design when you're an individual/small team building apps”