At least google will still walk back on things when they truly suck. Recent example is where they replaced the default Shopping, Images, Videos tabs when you search for something with autogenerated suggestions. It was awful. But, even though it took them a few months, that entire change seems to be reverted.
There is worth in the spiritual sense in that all living things are worthy and all of man are created as equals.
There is worth in a sociological sense in that a disabled person may be a positive contributor to the society in one way, but because of their disability cannot be in another. Similarly a niche artist is a positive contributor in their niche, where an unpopular artist indicates they may be considered less of a contributor than others.
In the sociological sense I would argue yes it is possible to compare “worth”.
This is the kind of thinking that leads to unmaintainable AbstractFactoriesFactory classes.
Sometimes allowing repeat code is good because two functions might drift away from common functionality in the future which would require a major rework of whatever abstraction you put over them to get them under the same roof.
Even in simpler cases it can be problematic. For example, refactoring a tiny bit of repetitive code into a separate function might seem like a good idea. But, over time, things diverge and now additional parameters and branches have to be introduced to support. A small amount of repeated code is optimal.
