Carol's Causal Conundrum: a zine intro to causally ordered message delivery
decomposition.al
decomposition.al
> "a small-circulation print or online publication that is produced through noncommercial means and is meant to appeal to a niche audience"
So then, is "causally ordered message delivery", "introduction to choreographic programming", and "Fighting Faults in Distributed Systems" too niche for HN? Hand-crafted with human sweat and tears, no AI. Is that the reason then perhaps for the silent comment thread, i.e. TL;DP, "too long, doesn't prompt"?
... And somewhat disappointed by the conclusions. A Java compiler (sans an overview of limitations/capabilities, but I understand the limitations of the format), and a... Haskell library, which, unfortunately, is incredibly irrelevant to me.
How is this subject approached in practice? I'm fairly familiar with authentication (generally handed off to a bespoke service + library that abstracts away most of this for the end programmer), but my generalist experience with other coordination problems between distributed systems is that programmers tend to not be particularly rigorous about them - and try their best to break down cross-service relationships to very, very simple-to-implement-in-a-bespoke-fashion cases.
"...and I"!!!
If you're going to make an effort to write, please don't grind me eyes