HN is technical but not that technical. Next time explain why "Affine MultiParty Session Types for Rust" are cool! And maybe how they relate to choreographies and choreographic programming.
You’re absolutely right that I led with terminology instead of value.
A simpler way to describe it is:
Hibana helps prevent protocol drift bugs in distributed systems.
You describe the interaction once as a global choreography, and each role gets a projected local API.
Because steps are affine (consumed once), invalid transitions like skipping, reusing, or taking the wrong branch are rejected by the type/protocol model.
So the practical goal is fewer hidden state-machine bugs, with one global source of truth for interaction order.
I appreciate the suggestion, and I’ll explain it this way in the next write-up.
HN is technical but not that technical. Next time explain why "Affine MultiParty Session Types for Rust" are cool! And maybe how they relate to choreographies and choreographic programming.
Thanks for sharing, this looks cool.
Thank you — this is very helpful feedback.
You’re absolutely right that I led with terminology instead of value. A simpler way to describe it is:
Hibana helps prevent protocol drift bugs in distributed systems. You describe the interaction once as a global choreography, and each role gets a projected local API. Because steps are affine (consumed once), invalid transitions like skipping, reusing, or taking the wrong branch are rejected by the type/protocol model.
So the practical goal is fewer hidden state-machine bugs, with one global source of truth for interaction order.
I appreciate the suggestion, and I’ll explain it this way in the next write-up.
[flagged]