As we automate more and more, and see claims of "one shotting" 80+yo maths conjectures, documenting and sharing what didn't work is surely going to get more and more important...
The Graph memory topology is an interesting idea... As is the idea of pushing all the nonlinear stuff into writes, leaving state evolution essentially linear (at least, by my read)
That's not Google. Buf.build is, hilariously enough, a completely separate company that tries to make sense of Google's protobuf, and it's doing a decent job from what I can see.
They reluctantly acknowledged that as a mistake by adding an actual "optional" modifier for field presence. proto3's previously so-called optional were really all present with a zero default value; proto2 could have supported that for required fields at the code level if they had wanted. In the end, all they've changed is how they frame the feature.
reply