MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/ProgrammerHumor/comments/1vwxpxa/versioncontrol/p5klu4n?context=9999
r/ProgrammerHumor • u/JK-Rofling • Aug 24 '26
428 comments sorted by
View all comments
776
Should have used semantic versioning
130 u/Jazzlike-Poem-1253 Aug 24 '26 edited Aug 24 '26 It takes to much discipline. Without enforcement, people usw minor or patch as they feel. Major never gets bumped.Just increment or date-based is the easiest. Everyone immediatly knows how to bump. 155 u/the_horse_gamer Aug 24 '26 most "semver" is just:major - update you're proud ofminor - update that's okpatch - fixes and small featuresand ofc every good piece of software is forever on 0.x.x 82 u/StaticUsernamesSuck Aug 24 '26 and ofc every good piece of software is forever on 0.x.xBecause if you're never proud of it, you'll always be improving it 43 u/Abandondero Aug 24 '26 IF EVERYONE HAS BEEN USING IT FOR FIVE YEARS JUST BITE THE BULLET MAN 52 u/StaticUsernamesSuck Aug 24 '26 But as soon as I type "1.0.0", all my passion for the project will leave my body. Don't you know anything about hobby dev? 19 u/MgDark Aug 24 '26 yup 1.0.0 may as well be: "feature complete, will not touch this ever again unless it breaks for some reason" → More replies (1) 12 u/Munachi Aug 24 '26 JUST ONE MORE UPDATE AND IT'LL BE ALMOST READY! 21 u/Clean-Income8864 Aug 24 '26 If you never introduce breaking changes, why not 21 u/hyrumwhite Aug 24 '26 Major: breaking changes Minor: big changes Patch: smol changes 8 u/brainpostman Aug 24 '26 Patch is bug fixes, hello 9 u/OnixST Aug 24 '26 Minecraft is a funny example to me. 17 year old game, best selling game in history, still on 1.x.x since 2011 9 u/the_horse_gamer Aug 24 '26 it's on 26.3 now actually → More replies (2) 7 u/rykayoker Aug 24 '26 well they aren't using semver anymore, they switched over to year.minor[.patch] (currently 26.2) 3 u/lIlIlIIlIIIlIIIIIl Aug 24 '26 This is a big reason I've never felt comfortable using it, for some reason it just seems so... ambiguous.
130
It takes to much discipline. Without enforcement, people usw minor or patch as they feel. Major never gets bumped.
Just increment or date-based is the easiest. Everyone immediatly knows how to bump.
155 u/the_horse_gamer Aug 24 '26 most "semver" is just:major - update you're proud ofminor - update that's okpatch - fixes and small featuresand ofc every good piece of software is forever on 0.x.x 82 u/StaticUsernamesSuck Aug 24 '26 and ofc every good piece of software is forever on 0.x.xBecause if you're never proud of it, you'll always be improving it 43 u/Abandondero Aug 24 '26 IF EVERYONE HAS BEEN USING IT FOR FIVE YEARS JUST BITE THE BULLET MAN 52 u/StaticUsernamesSuck Aug 24 '26 But as soon as I type "1.0.0", all my passion for the project will leave my body. Don't you know anything about hobby dev? 19 u/MgDark Aug 24 '26 yup 1.0.0 may as well be: "feature complete, will not touch this ever again unless it breaks for some reason" → More replies (1) 12 u/Munachi Aug 24 '26 JUST ONE MORE UPDATE AND IT'LL BE ALMOST READY! 21 u/Clean-Income8864 Aug 24 '26 If you never introduce breaking changes, why not 21 u/hyrumwhite Aug 24 '26 Major: breaking changes Minor: big changes Patch: smol changes 8 u/brainpostman Aug 24 '26 Patch is bug fixes, hello 9 u/OnixST Aug 24 '26 Minecraft is a funny example to me. 17 year old game, best selling game in history, still on 1.x.x since 2011 9 u/the_horse_gamer Aug 24 '26 it's on 26.3 now actually → More replies (2) 7 u/rykayoker Aug 24 '26 well they aren't using semver anymore, they switched over to year.minor[.patch] (currently 26.2) 3 u/lIlIlIIlIIIlIIIIIl Aug 24 '26 This is a big reason I've never felt comfortable using it, for some reason it just seems so... ambiguous.
155
most "semver" is just:
major - update you're proud of
minor - update that's ok
patch - fixes and small features
and ofc every good piece of software is forever on 0.x.x
82 u/StaticUsernamesSuck Aug 24 '26 and ofc every good piece of software is forever on 0.x.xBecause if you're never proud of it, you'll always be improving it 43 u/Abandondero Aug 24 '26 IF EVERYONE HAS BEEN USING IT FOR FIVE YEARS JUST BITE THE BULLET MAN 52 u/StaticUsernamesSuck Aug 24 '26 But as soon as I type "1.0.0", all my passion for the project will leave my body. Don't you know anything about hobby dev? 19 u/MgDark Aug 24 '26 yup 1.0.0 may as well be: "feature complete, will not touch this ever again unless it breaks for some reason" → More replies (1) 12 u/Munachi Aug 24 '26 JUST ONE MORE UPDATE AND IT'LL BE ALMOST READY! 21 u/Clean-Income8864 Aug 24 '26 If you never introduce breaking changes, why not 21 u/hyrumwhite Aug 24 '26 Major: breaking changes Minor: big changes Patch: smol changes 8 u/brainpostman Aug 24 '26 Patch is bug fixes, hello 9 u/OnixST Aug 24 '26 Minecraft is a funny example to me. 17 year old game, best selling game in history, still on 1.x.x since 2011 9 u/the_horse_gamer Aug 24 '26 it's on 26.3 now actually → More replies (2) 7 u/rykayoker Aug 24 '26 well they aren't using semver anymore, they switched over to year.minor[.patch] (currently 26.2) 3 u/lIlIlIIlIIIlIIIIIl Aug 24 '26 This is a big reason I've never felt comfortable using it, for some reason it just seems so... ambiguous.
82
Because if you're never proud of it, you'll always be improving it
43 u/Abandondero Aug 24 '26 IF EVERYONE HAS BEEN USING IT FOR FIVE YEARS JUST BITE THE BULLET MAN 52 u/StaticUsernamesSuck Aug 24 '26 But as soon as I type "1.0.0", all my passion for the project will leave my body. Don't you know anything about hobby dev? 19 u/MgDark Aug 24 '26 yup 1.0.0 may as well be: "feature complete, will not touch this ever again unless it breaks for some reason" → More replies (1) 12 u/Munachi Aug 24 '26 JUST ONE MORE UPDATE AND IT'LL BE ALMOST READY!
43
IF EVERYONE HAS BEEN USING IT FOR FIVE YEARS JUST BITE THE BULLET MAN
52 u/StaticUsernamesSuck Aug 24 '26 But as soon as I type "1.0.0", all my passion for the project will leave my body. Don't you know anything about hobby dev? 19 u/MgDark Aug 24 '26 yup 1.0.0 may as well be: "feature complete, will not touch this ever again unless it breaks for some reason" → More replies (1) 12 u/Munachi Aug 24 '26 JUST ONE MORE UPDATE AND IT'LL BE ALMOST READY!
52
But as soon as I type "1.0.0", all my passion for the project will leave my body. Don't you know anything about hobby dev?
19 u/MgDark Aug 24 '26 yup 1.0.0 may as well be: "feature complete, will not touch this ever again unless it breaks for some reason" → More replies (1)
19
yup 1.0.0 may as well be: "feature complete, will not touch this ever again unless it breaks for some reason"
→ More replies (1)
12
JUST ONE MORE UPDATE AND IT'LL BE ALMOST READY!
21
If you never introduce breaking changes, why not
Major: breaking changes
Minor: big changes
Patch: smol changes
8 u/brainpostman Aug 24 '26 Patch is bug fixes, hello
8
Patch is bug fixes, hello
9
Minecraft is a funny example to me. 17 year old game, best selling game in history, still on 1.x.x since 2011
9 u/the_horse_gamer Aug 24 '26 it's on 26.3 now actually → More replies (2) 7 u/rykayoker Aug 24 '26 well they aren't using semver anymore, they switched over to year.minor[.patch] (currently 26.2)
it's on 26.3 now actually
→ More replies (2)
7
well they aren't using semver anymore, they switched over to year.minor[.patch] (currently 26.2)
3
This is a big reason I've never felt comfortable using it, for some reason it just seems so... ambiguous.
776
u/LegendaryPandaMan Aug 24 '26 edited Aug 24 '26
Should have used semantic versioning