> That wasn’t the question Yes, it was. While the grammar I used should be pretty clear on what I meant already, here’s an alternative version: Why would usin

> That wasn’t the question Yes, it was. While the grammar I used should be pretty clear on what I meant already, here’s an alternative version: Why would using semantic versioning (something near universally accepted as a best practice) be flawed in your eyes? Or more simply: Why would using semantic versioning be flawed in your eyes? > These are basic facts. Actually, they aren’t. It’s your opinion (not a fact) and you still haven’t provided a single drawback (flaw) to following semantic versioning despite repeated requests. > Have you read the semver spec? Yes, I have. More than once in fact. Have you? > Is your libraries new version compatible with my library? Assuming both authors follow semantic versioning faithfully and the previous minor/patch release worked, then yes, it very likely will be compatible. > How can you know? If both sides have a well defined API and the authors follow semantic versioning, you should have a good indication that way. That said, as the saying goes, “trust but verify”.