What the hell happened to versioning?
I think Chome was the first software that I can recall which changed version number all the time.
And it feels like almost everyone is doing it these days.
Yeah once Chrome started this shit Firefox went up like 40 versions in just a few months. It's a fucking meme
>>54654111
That way pajeets software is looking dynamically evolving while it's remaining a pile of poo.
>>54654111
blink is shit
ill just leave this here
because people are fucking stupid and don't care about proper software engineering conventions.
>Blink version 537
http://semver.org/
big number = better than
>>54654656
>>54654737
you laugh at me because i'm different ; i laugh because i'm at home watching family guy. expecto patronum
I don't even work in electronic tech and I still version control everything. So much easier to stay in sync with people with whom I share documents, plus I have a log of changes (and most importantly who told me to make them). Granted I don't go into four-digit build numbers but it's nice to tell from the name of a document which stage of a project it belongs to.
>What if I want my API version numbers to be low?
>That is silly, aesthetics have little place in versions where the point is to convey semantic information. If you want lower version numbers, get your API right earlier.
http://blog.appliedcompscilab.com/monotonic_versioning_manifesto/
Is there really anything wrong with the rolling release model?
>>54654111
Bigger version numbers look impressive than slight decimal increments.
What looks better? 3.21.2 -> 3.21.3 or Version 50?
>>54656110
Version 50 looks too edgy and unreliable. While 3.21.2->3.21.3 looks like rock-solid stability of development cycle and much likely you won't end up in a situation when developer has just suddenly decided to change fucking everything and now nothing works for you.
