Comment by BoorishBears
3 days ago
I disagree. The bare minimum they could have done in all these years was build a proper high quality, tightly coupled component library instead of riding this "copy paste your way to a result" trend.
Not stuff like shadcn and Tailwind Catalyst, but a proper versioned, tightly coupled UI library with rich theming capabilities made for the 99% of users who aren't skilled enough at design to be cobbling together their own design systems or editing a Button component directly.
Instead they rode the wave (despite being best positioned to redirect the wave) and they're paying the price.
If it wasn't AI it'd be the first version of MUI that moves on from Material Design 2 as a default. Or Hero UI v3. Or literally anyone who brings sanity back to the space of component libraries and leaves "copy and paste code snippets" behind
I don't understand how a component library would be AI-proof in a way CSS templates are not.
There are more knobs to turn when you have an actual library, and you become a lot less fungible than a random collection of TW classes.
HeroUI faces the same problem, and now their React Native library includes an optional (paid) conpiler solution that makes it faster.
MUI has the same problem but besides templates they have their MUI X data components which aren't limited in complexity to what can be ergonomically copy and pasted to a clipboard.