-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
> I'm not saying major version bumps should be avoided at all costs - but they should be avoided at /some/ costs. We should aspire to design our APIs well enough that we don't have to later break them and force our users to upgrade. That's clearly impossible to always hold to, which is why we have major version bumps - but major version bumps should be rare and apologetic, not careless and frequent.
This is exactly what I'm talking about.
If the tweet had said "breaking changes should not be careless and frequent", this post would not exist and those replies would not exist because... it's so painfully obvious!
You really think people are arguing against that?
That is simply not what the original comment says! That's not even what you said at the start of your own comment just now! It is not the same as saying "you got the API wrong"!
-
And I don't mean that in a semantical "haha gotcha" way, I mean they literally are two different statements and one is wrong, and one is so obvious it's literally part of the standard!
I mean have you actually read the document that defines SemVer?!
https://semver.org/
It literally says in 10 different ways that you should not be breaking your API often! That if you are either you need to stay below 1.0.0 or use a separate branch.
-
It's like by saying (or supporting) a viewpoint so extreme it's straight up wrong, you position yourself to then retroactively take an extremely moderate position in a way that makes you sound super clever...
Except you needed to support/say something super unclever as a spring board. And anyone who's gone through enough if these kinds of platitudes will see that immediately and call you out on the unclever thing you said.
That's why you see such strong opposition, not because a senior ASF contributor needs you of all people to tell them that major version bumps in semver, aka breaking changes, shouldn't be careless and frequent!
Do you not see what you're doing as patronizing at all? Luring people in with a conversation about a downright bad take (even if it's someone else's) then browbeating them with a super obvious non-statement that would never have been worth the conversation in the first place?
It's the worst form of ego-stroking if I'm being real for a second. Don't do that.
I strongly encourage people to use ComVer instead: https://gitlab.com/staltz/comver