this post was submitted on 01 Oct 2026
927 points (98.7% liked)
Programmer Humor
33426 readers
1606 users here now
Welcome to Programmer Humor!
This is a place where you can post jokes, memes, humor, etc. related to programming!
For sharing awful code theres also Programming Horror.
Rules
- Keep content in english
- No advertisements
- Posts must be related to programming or programmer topics
- If the mod doesn't find it funny, you're banned. Ha-ha!... For real: do not use the community for "statements". There are other places for such content. Keep it chill and funny.
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I've started using CalVer (so a relase in October 2026 would be numbered 26.10). This is just so much better for end-user applications.
What's the benefits here? Why is the semver even bad to begin with? I'm not sure why I'd care that it's in the hundreds. It's a number, right?
Dates - I can just look at the release date if I want that.
SemVer simply has no meaning to end users.
By definition, SemVer is supposed to have meaning to end users. If you see the third number increase, no worries, it's just bugfixes.
If you see the second number increase, well, in theory no worries, it's just cool new features but doesn't break anything you were doing, whatever you were doing should keep on working as always, and you can explore the new features at your leisure.
The first number changes: beware, something you may be used to can change/go away so it's not necessarily a slam dunk to update that.
The problem is that many projects just call it SemVer when they just play with arbitrary numbers. I'll call it "Marketing Versioning".
you can tell SemVer works because this is the first time i’ve ever seen it explained, but i already understood all of it just from using programs (and reading changelogs)
You know that puts you so far above average, you're pretty much an outlier though... right? 😅
In a GUI application every change is a breaking change...
You leave Visual Basic alone!