I wonder how these could tie in w/ Resiliant Distributed Datasets in Spark? It seems as though they could have addressed some of the possible improvements mentioned in section 2.

I’m also curious how C-CRDT’s clean themselves up over time. Maintaining state monotonically will present some memory issues. Could TTLs be set, or could garbage collection be triggered somehow?

Is it just me, or is the bolt/spout terminology in section 6 (Word Count) backwards?

I’m rewriting my Erlang version management tool (erln8). Originally, it was written in C w/ glib, but the code was somewhat unmaintainable. Moving to C++/Boost has been great, and significantly cut down the amount of code I need to support.