ZILtoid1991@lemmy.world to Programmer Humor@programming.dev · 4 days agoQuick, someone release Chatbot 2000!lemmy.worldimagemessage-square14linkfedilinkarrow-up14arrow-down10
arrow-up14arrow-down1imageQuick, someone release Chatbot 2000!lemmy.worldZILtoid1991@lemmy.world to Programmer Humor@programming.dev · 4 days agomessage-square14linkfedilink
minus-squareblackshirt@lemmy.worldlinkfedilinkarrow-up1·3 days agoChrome bumped its versioning numbers to overtake Firefox back in the day, that’s how we ended up with stupid version numbers like 124.1.2 instead of meaningful versions.
minus-squareMorlark@feddit.uklinkfedilinkarrow-up1·1 day agoAnd then Firefox changed its version numbering policy to “catch up”. I lost a shred of respect for them that day.
minus-squareteolan@lemmy.worldlinkfedilinkarrow-up0arrow-down1·3 days agoI’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.
minus-squareMonkderVierte@lemmy.ziplinkfedilinkarrow-up0·3 days agoBecause it’s clearly not 1926 and it likely will not be around in 2126.
minus-squareteolan@lemmy.worldlinkfedilinkarrow-up1·edit-23 days agoMaybe the software will be around in 2126, but I most certainly won’t, not my problem 😂
Chrome bumped its versioning numbers to overtake Firefox back in the day, that’s how we ended up with stupid version numbers like 124.1.2 instead of meaningful versions.
And then Firefox changed its version numbering policy to “catch up”. I lost a shred of respect for them that day.
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.
Why not just do 2026.10 then?
Because it’s clearly not 1926 and it likely will not be around in 2126.
Maybe the software will be around in 2126, but I most certainly won’t, not my problem 😂