You can find a few implementations (1, 2) to play with now if you’re interested…
I found the video series [3] in the latter particularly interesting in trying to understand it, if you’re game to sit through a few hours of live stream.
Edit: I’m apparently wrong on the “abandoned” part. The author of this repo wants to maintain it and accepts bugs and issues on github, https://news.ycombinator.com/item?id=28025692
Holy moly your bar for "complaining" is low. It'd be like if I were hiking in the woods, overheard someone talking about crossing a bridge, and said "careful, that bridge isn't very sturdy!" and you respond "How about contacting your local ranger station, submitting a form BQ-447r with your real name and contact info, including a structural analysis of exactly where you see the issue, and sitting through multiple council meetings about the issue, instead of complaining!?"
GP's not really complaining, they're just warning people. And the reality is that submitting an issue can take a lot of time. I don't even bother submitting bug reports to Microsoft anymore because their burden for reproducibility is so high that they're basically asking me to reverse-engineer their software to find their bug for them.
You can find a few implementations (1, 2) to play with now if you’re interested…
I found the video series [3] in the latter particularly interesting in trying to understand it, if you’re game to sit through a few hours of live stream.
[1] - (rust) https://github.com/dkellner/chronofold
[2] - (js) https://github.com/jmatsushita/purescript-chronofold
[3] - https://m.youtube.com/watch?v=gg5q_V7tBjE&pp=sAQA