|
|
|
|
|
by jjani
444 days ago
|
|
> They don't have a design system, don't know what that even means, and their sinful hands should not be tweaking any UI libraries, at most being limited to modifying a rich set of theme tokens that force consistency I feel like the majority of shadcn users doesn't tweak it whatsoever though. In fact - I bet you a large percentage has never even considered the ability to tweak it, just seeing it as a plug-and-play set of UI components. Think old Android and iOS apps, where almost everyone just used the default components. |
|
> You could have even made the default theme shadcn-like to satisfy all the people lying to themselves that one day they'll actually modify that ui folder.
That's why shadcn is so terrible: you're resorting to diffs and a loose convention instead of a stable API and a package manager, for the promise that one day you can definitely probably modify it into something else... yet if you're the kind of person to start with shadcn/ui instead of Radix, you shouldn't be modding components in the first place.
Even if you get real designers later, they're not going to try and "evolve" shadcn into your brand, they're going to start from scratch and you're back at Radix again.