Post B6toXJm2iLywr33Fia by neauoire@merveilles.town
 (DIR) More posts by neauoire@merveilles.town
 (DIR) Post #B6toXJm2iLywr33Fia by neauoire@merveilles.town
       0 likes, 0 repeats
       
       Uxn, Uxntal and Varvara's Kelvin Versioning https://lists.sr.ht/~rabbits/uxn/%3C30f763a6-7118-4a99-84b7-8227627bcc57@xxiivv.com%3E#uxn
       
 (DIR) Post #B6ttjDhrb9KjHaaj4K by h3rald@merveilles.town
       0 likes, 0 repeats
       
       @neauoire Kelvin versioning is actually a fantastic idea. It should be more common for certain things for sure, like programming languages, compilers, assemblers and infrastructure in general. With a bit of luck, with the way things are going in the world, it may as well end up being the preferred versioning system for artisan/human-made software. Day after day, I find myself longing for software that reaches maturity and stability above all else.
       
 (DIR) Post #B6u2qQjcSNfvItvRUe by neauoire@merveilles.town
       0 likes, 0 repeats
       
       @h3rald let's start a trend!
       
 (DIR) Post #B6u5NeiFhwfm7WFziy by kirtai@tech.lgbt
       0 likes, 0 repeats
       
       @neauoire For some reason I'm reminded of how TeX uses digits of Pi and Metafont uses digits of e.I know they're not the same but I find it interesting :neocat_3c:
       
 (DIR) Post #B6u5Neuexob6k03u40 by neauoire@merveilles.town
       0 likes, 0 repeats
       
       @kirtai I came across it looking around for interesting versioning schemes! It's such a cool idea haha, each version adds 1 byte of data to your project ;)
       
 (DIR) Post #B6uBDaLRgxsvP2Add2 by aartaka@merveilles.town
       0 likes, 0 repeats
       
       @neauoire oh, that looks really good! I like how it promotes slowness and deliberation! I myself was planning a versioning system like so: there’s a “release” every month, containing arbitrary number of bug fixes. But only 0/1 feature. Yes, one feature per month, no more! That’d provoke a thorough process of feature vetoing and community moderation, while still allowing progress.I wanted to use that for my GUI toolkit, knstrktr, but it’s slightly postponed / being redesigned for now.
       
 (DIR) Post #B6vRglQfLwrebPVXX6 by abrenon@universites.social
       0 likes, 0 repeats
       
       @neauoire Very inspiring idea! Thanks for sharing. How should I go about estimating the temperature of a given project? I've just started a project, is it at 100K ? 2048K ? What happens if you end up needing 60 changes in your 54K project example? Would there be a 1.5K version somewhere along the line? How does your strategy relates to the versioning strategy consisting in slowly approximating pi's decimals?
       
 (DIR) Post #B6vRglqBp3HTsZRvJg by neauoire@merveilles.town
       0 likes, 0 repeats
       
       @abrenon so the project is now 3 years old, and I have a pretty good idea of the rate of cooling by that time, and I used that to estimate the amount of changes left based on the prior rates of changes. For an altogether new project, I'd start by comparing it to other projects of the same type and see how many changes it took them before stabilizing and use that as my starting number, the number of commits maybe?
       
 (DIR) Post #B6vTWcMqOB8pVj0f6u by abrenon@universites.social
       0 likes, 0 repeats
       
       @neauoire Makes sense! : ) Reading your answer I feel a bit stupid: evaluating the total amount of work required before starting is something engineers are supposed to master, but in my experience it's so hard to get it right that the idea of knowing in advance the number of commits looked terrifying. Your versioning scheme looks like a great way to develop this skill and to keep this objective in mind.
       
 (DIR) Post #B6vTWcjt0VZafBn41g by neauoire@merveilles.town
       0 likes, 0 repeats
       
       @abrenon we'll see! Like I said, it's an experiment, this might fail horribly, but I want to find out : )