4 ms·
Well, it's up to you to interpret the libyears how you like. It doesn't have to be that more libyears is worse, but it will mean that you're missing X libyears
by stavros 3y ago
Well, it's up to you to interpret the libyears how you like. It doesn't have to be that more libyears is worse, but it will mean that you're missing X libyears of security updates (and also X libyears of potential new bugs).
- edflsafoiewq 3y agoWell, no you can't. Adding them together implicitly affirms that libyears from different dependencies are equivalent.
- stavros 3y agoYes it does. And you can say "this project has more libyears, so it's more mature".
- IanCal 3y agoThat really doesn't follow. A barely maintained mess of a personal project running for 10 years is not more mature than a 7 year project heavily developed and released by a high quality team, with 3 years of stability in the main API and in use around the world.
- bmacho 3y agoYes, that's the point of the metric. The observation that libyear is a dimension, libyears are additive. If you value some library years more, and some less, then weight the sum. It's like saying there is no point of natural numbers, because when you count apples, some apples might be rotten.
- edflsafoiewq 3y agoIt's saying you can't add different units together.