refusing to follow semantic versioning standards that are designed to essentially account for that is pants-on-head stupid.
Seems like it would be a bit hard to follow a versioning scheme that it predates by almost 20 years. Lua 5.2 even predates semver 1.0.0.
Before semver there was basically no standardization in versioning schemes and the meaning that semver applied to version numbers basically didn’t exist (at least in my experience) before it came around. Everyone just kinda had their own meaning for what version numbers meant.
semantic versioning wasn’t a new concept when semver 1.0.0 was released. Before that lot of projects already followed this scheme and this was just made official so that everyone should follow it as the standard. So its kind of like if all web browsers support non standard features, and then the committee decides to add it to the standard to make it official. My point is, that the release of semver 1.0.0 isn’t the invention of it.
Seems like it would be a bit hard to follow a versioning scheme that it predates by almost 20 years. Lua 5.2 even predates semver 1.0.0.
Before semver there was basically no standardization in versioning schemes and the meaning that semver applied to version numbers basically didn’t exist (at least in my experience) before it came around. Everyone just kinda had their own meaning for what version numbers meant.
Ok that’s actually an excellent point that I hadn’t accounted for lol
semantic versioning wasn’t a new concept when semver 1.0.0 was released. Before that lot of projects already followed this scheme and this was just made official so that everyone should follow it as the standard. So its kind of like if all web browsers support non standard features, and then the committee decides to add it to the standard to make it official. My point is, that the release of semver 1.0.0 isn’t the invention of it.