Someone commented on our latest Youtube vid about 1.4, and brought up a truly excellent point that I wish to relay and add to here.
Soylent is obviously being versioned like software, and is clearly being developed by (and even for) software engineer types. So why doesn’t it also get released like software?
I’m sure there would be all sorts of logistical challenges to this, but imagine if there was a “stable branch” (that would probably be 1.3 at this point), a “current branch” (1.4) and a “development branch” (possibly available in limited quantities and only for those who really want to be on the bleeding edge). You could choose what you wanted to order (maybe dev branch is only available to existing customers?) and subscribe to. For instance we would have a “stable branch subscription” and so would still be on 1.3 until and unless we chose to order some 1.4 to see if we like it.
Branches would not change until there was an overwhelming consensus from the community that the latest branch was worthy of being called “stable”. So for instance, 1.0 would have been stable (such as it can be for a first release), and 1.1 would have been latest. Consensus in the community was not good on 1.1, so 1.2 would have become latest, and 1.0 would have stayed stable. Consensus on 1.2 was certainly more positive than 1.1 and 1.0 and in fact I don’t think anyone who was fine with 1.0, had issue with 1.2. So 1.2 would have become the stable branch as soon as 1.3 came out as the new latest release. 1.3 proved itself very quickly and would have become the new stable branch and 1.4 would have been latest. Those of us for whom 1.4 is not working, wouldn’t have to worry about a thing since we’d be staying on 1.3. When 1.5 comes out it would be the latest and 1.3 would remain stable until and unless 1.5 proved itself within the community.
If this is truly going to be the software of food, I think it needs to really, truly, be handled like it… for all our sakes.