4 ms·
I think it's worked out pretty well in ruby. Which I believe is the ecosystem the semver inventer was working in when he invented it, so maybe that's why it's a
by jrochkind1 8y ago
I think it's worked out pretty well in ruby. Which I believe is the ecosystem the semver inventer was working in when he invented it, so maybe that's why it's a good fit.
While certainly not perfect, I think semver has greatly eased dependency management in ruby ecosystem.
Certainly more sophisticated forms of machine-readable change information would be useful, if feasible to implement and maintain at a justifiable cost for the benefit provided. But that's no reason not to use a simpler thing that helps.
Unless it is making dependency management _harder_ in some ways in some ecosystems. (Or perhaps making it no easier or harder, but at significant expense, or the cost of confusing devs as to what's going on). That would be an interesting argument. This post didn't make it or provide any such examples from actual experience or with concrete context.
What matters is if it helps or hurts or does nothing in actual practice, which is tricky because you it's hard to know that in the hypothetical, you need a dependency ecosystem where large numbers of maintainers are trying to use semver to know, instead of just be trying to predict, how it's working out. But we have several of those now. What ultimately matters is if it's helping or not. I think it is helping significantly.