cdc-file-transfer VS d2

google/cdc-file-transfer: Tools for synching and streaming files from Windows to Linux (github.com)

I have been reading about contend defined chunking. If you look at Google's cdc-transfer and other tools that use content-defined-chunking (e.g. restic, kopia, borg), they talk about how great CDC is for insertions that would otherwise shift the boundaries.

While I am no fan of Google or Stadia, this is wrong. They open sourced the CDC file transfer software they used for syncing files from Windows to Linux.

The README has pretty good explanation of why it's better than rsync, and the animations help show exactly what the difference is.

While not embedded in markdown, I like d2 [1]. I can use it with org-babel to embed and view the diagrams on emacs. After using graphviz for years, the visual output seems more polished to me. With that said, I want to give pikchr a try.

[1]:https://d2lang.com/

In the next post I'll deep-dive into the D2 language which also has a huge set of features. Stay tuned.

That site is created by the maintainers of D2[1], so it might be biased, but I still think D2 has the friendliest syntax of the bunch, including nomnoml.

[1]: https://d2lang.com/

I've been using https://structurizr.com/ to automatically generate C4 diagrams from a model (rather than drawing them by hand). It works well with the approach for written documentation as proposed in https://arc42.org/. It's very easy to embed a C4 diagram into a markdown document.

The result is a set of documents and diagrams under version control that can be rendered using the structurizr documentation server (for interactive diagrams and indexed search).

I also use https://d2lang.com/ for declarative diagrams in addition to C4, e.g., sequence diagrams and https://adr.github.io/ for architectural decision records. These are also well integrated into structurizr.