This really does seem like a JavaScript/frontend kind of thing.
Sure, after all CSS allows you an infinite array of aesthetical choices and JS an infinite array of behaviors.
Some UI libraries are basically frameworks and they require the developer to marry the philosophy. That's also probably why there are so many, different ways of solving the same problem.
It's hard to say definitively why it's not ideal, but it seems like there is a lot of wasted energy in frontend land trying to keep up with what's going on.
I also see a lot of wasted energy into solving the same problem over and over. If you think about it, most of all those libraries have: buttons, inputs, ways to display errors, probably a grid based responsive layout, modals, a table and so on.
I'm not saying there's anything wrong either, it's just that... I don't know... it's a feeling
Sure, after all CSS allows you an infinite array of aesthetical choices and JS an infinite array of behaviors.
Some UI libraries are basically frameworks and they require the developer to marry the philosophy. That's also probably why there are so many, different ways of solving the same problem.
I also see a lot of wasted energy into solving the same problem over and over. If you think about it, most of all those libraries have: buttons, inputs, ways to display errors, probably a grid based responsive layout, modals, a table and so on.
I'm not saying there's anything wrong either, it's just that... I don't know... it's a feeling
CV driven development?