I think this emperor has no clothes! Take distributed concensus protocols: two-phase-commit (or RAFT et al). I have never worked in an organization that adopted

I think this emperor has no clothes! Take distributed concensus protocols: two-phase-commit (or RAFT et al). I have never worked in an organization that adopted a 2PC communication protocol. The only real-world example I know is a wedding ceremony: "Do you Jane, take Tarzan to be your ape-man? (Jane says 'I do') And do you Tarzan, take Jane to be your swinging partner (Tarzan says 'Woo hoo!'). I now pronounce you husband and wife (because you've each locally committed)" Can you imagine working in a place like that? And yet 2PC is part of most database design. Or take a design that consists of functional transformations of a sequence of ASTs. What organizational communication structure is stateless? ("Don't tell me you already told me that a minute ago! I refuse to remember anything you say. ever. You want to tell me something, start from the beginning every time. And furthermore, I refuse to talk to you at all unless we're given an entirely new language in which to express our conclusions. Besides, you're nothing but a monad to me") Ridiculous for human communication, but arguably essential for large-scale distributed parallel computation. Or take event-bubbling, or model-view-controller. Does any organizational communication system use those in anything other than a once-in-a-blue-moon, accidental way?