Footkerchief

"Threat" is a correct term for an attempt to compel action via potential negative consequences.

Seems like that would include all fermented foods.

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?

TLDR: you can put tablets of mosquito-killing bacteria in buckets.

It's probably better for Wikipedia's quality if editors remain unsung, rather than it being status-conferring.

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.

You still use constraints even if you put all your business logic in stored procedures.

When did clickbait headlines become acceptable here?

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.

Horseshoe theory addresses this.

Can you provide an example with details? Thanks!