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

FULL DISCUSSION
 

I don't see a problem with having competing implementations, as every instance is an oppprtunity to discover a good approach to express and compose UI components.

What I have a problem with is people choosing a library as if it were a framework by tightly coupling to it before verifying that it fits their requirements, both at present and at any point in the future.

Any library listed here should be replaceable if need be. If that's not the case for the project in question, any change in requirements will mean the project needs to basically start the UI from scratch.

 

Any library listed here should be replaceable if need be. If that's not the case for the project in question, any change in requirements will mean the project needs to basically start the UI from scratch.

Yes and no, depends on how much custom code you have.

You might have to rewrite your custom "button widget" that uses X to use Y, fix the JS code (because maybe the name of the event you're handling has changed), fix the customizations and so on.

It's doable, but it's never going to be free.

code of conduct - report abuse