|
|
|
|
|
by jjani
438 days ago
|
|
> satisfy all the people lying to themselves that one day they'll actually modify that ui folder. What I'm saying - they're not lying to themselves that they'll do that. They've never even considered it as being something to potentially do! They consider it as a package to use as-is. "A re-design later on? Who knows, by that time we'll have people who know their UI stuff, they'll figure it out. Whether that will be based on shadcn? Who cares, not important." I bet the premise that all these people are using shadcn with the idea of some day modifying it just isn't the most common reality. |
|
The main selling points and source of shadcn's meteoric rise...
- It's not a component library!
- It's easy to customize!
- You just Ctrl + C, Ctrl + V!
- You can just edit it in your project!
- No more fighting themes!
- It's a kickstarter for your design system! (contrary to my words that you're repeating, many people choose shadcn/ui thinking it is going to make a meaningful difference in starting their own design system, people who have no business starting design systems especially)
> I bet the premise that all these people are using shadcn with the idea of some day modifying it just isn't the most common reality.
The thing is literally distributed via copied files and updated via diffs instead of being a package. The entire cargo cult that lead up to that is 100% the idea they'll modify it. It's just either don't out of apathy (and should have just used a component library), or do and do so terribly (and should have just used a component library).