It is perfectly reasonable and avoids mistakes. It's better to have a module that's unused than to break your whole build. If you want to try something install

It is perfectly reasonable and avoids mistakes. It's better to have a module that's unused than to break your whole build. If you want to try something install it and then remove it. That's the more conscious decision. I don't want to have to remember to save the module if I end up liking it, but I will remember to remove it when tearing it down from the codebase, and if I don't, nothing bad happens.