A CRDT is a purely technical construct! Correctness (in terms of merge conflicts) is well-defined in that context and it's orthogonal to any kind of semantic/ap

A CRDT is a purely technical construct! Correctness (in terms of merge conflicts) is well-defined in that context and it's orthogonal to any kind of semantic/application definition! This is a bonkers conversation. It's like claiming integer division isn't correct because 5/2 should be 2.5 instead of 2.