re: How many UI libraries are too many? VIEW POST


Wow. I mean, wow. A 'curated' list of framework component libraries? What about all the libraries that didn't meet the curator's high standards?

'Framework component libraries'? So not only do I get to pick my ghetto when I choose a frontend framework, but now I can add another ghetto inside my ghetto when I choose a component library? How on earth is this a good idea?

Sure, you can probably switch one out for another, but it's not going to be zero cost. Nobody ever thinks of the downsides.

Read a nice post today by Daniel Westheide called The Complexity Trap. Feels relevant.

code of conduct - report abuse