There is a catch though - we use it only as a code review platform. It always seemed to be focused on that part more than in any other. I'm not saying everything else is bad, it just a gut feeling that code review always got the maximum attention.
And another catch is that it seems they lost their momentum even in this area. I recall times when we waited for weekly status update to see if there is something we'd have as excuse for an upgrade. Now it's even not a weekly update and speed of development seems to be slow.
Off topic: considering you've left BitKeeper and you were one of the most active developers in user forum, what's the status of BitKeeper? Is it still developed* or it's in maintenance mode for existing commercial clients?
* yes, it's open source, but being open source and "you can add any feature yourself" doesn't imply there is a momentum behind and a kind of "directed" force to move it forward
One of the major selling points of that utility coin was that it'll be automatically available for 200M active users of Telegram. Frictionless entry point into coins is a huge step forward.
> The lock file stops future upgrades; once it is written, your build stays on serde 1.0.27 even when 1.0.28 is released.
That means that the only difference is that `vgo` doesn't require lock file for reproducible builds, now the question is what's considered so terrible wrong/dangerous with having a lock file?
I'd say that post actually makes a bit different point: while Docker might be good for developers, it's failing on production "side" of things. And that has a completely different set of requirements than CI servers with multiple versions on SQL engines.
I'm asking as I would like to try, but I'm confused by wording in GH issue saying that this specific model is kind of lost