Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

100% Positive

Analyzed from 193 words in the discussion.

Trending Topics

#components#code#more#traditional#component#expected#why#shadcn#customize#options

Discussion (9 Comments)Read Original on HackerNews

_34516 minutes ago
What inspired you to make this?
benswerd11 minutes ago
gonna use it on my websites homepage
techpression11 minutes ago
I fully expected this to be complements for the output you get from those tools for some reason, that AI generated look. No idea why anyone would want that though.
sim04fulabout 1 hour ago
I love this!
dprkhabout 2 hours ago
Why did you choose to use shadcn registry?
benswerdabout 2 hours ago
Generally, when using these components I ended up wanting to customize a lot. I switched around the options, coloring, the words in the loading, I mix and matched the components from different CLIs, etc.

I think these are more useful as baselines than as final destinations, and I expect production users to customize them far more than options in components.

I also separately don't really believe in traditional components anymore, code is cheap. The value in these components is that I took the time to pixel match a bunch of the CLIs, not the specific interface used to integrate them.

tipiiraiabout 1 hour ago
What are traditional components? How are untraditional better?
benswerdabout 1 hour ago
Think MUI, heroUI, traditional components have you install their package, import the component and configure it through arguments.

ShadCN components have you copy the component code into your codebase, you own it. They come with the ability to configure arguments, but also because the code is yours its expected that you change the internal logic/styling/structure of the component.

I believe in the era of AI code the ladder just makes more sense.