Exactly. Use a fancy expressive structure if you want, but don't try to abstract away the mapping between that and the general-purpose code that it relies on. "Each domain has its own rules"? How would I even know where to look for those?
Yes, these comments are necessary pushback against the habit of these disciplines to push interventions that don't work because their evidentiary standards are bad.
Surprised to see no discussion of other data structures like dicts/maps, or arrays of arbitrary type. Hopefully they'd be a straightforward extension. IME, apps need collaborative data structures more often than they need pure collaborative text editing.
The motivating examples (update validation, partial loading, higher-level operations) are interesting, but I don't see a strong case that the reason Yjs etc. lack these features is the underlying CRDT implementation, as opposed to these features being intrinsically difficult to build.
"Condemn firing" is a misleadingly narrow headline that focuses undue attention on the resign/fire question. The important part of the story is not the HR machinations of her departure, but what caused the situation to escalate to that point. The letter itself makes this clear -- its condemnations and demands go way beyond Gebru's employment:
> Dr. Gebru has faced defensiveness, racism, gaslighting, research censorship, and now a retaliatory firing
The letter goes on:
> In late November, five weeks after the piece had been internally reviewed and approved for publication through standard processes, Google leadership made the decision to censor it, without warning or cause.
The demands are also not about the firing itself:
> explain the process by which the paper was unilaterally rejected by leadership
https://www.theguardian.com/world/2008/mar/19/japan