{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreic4nxpypmhaq5wp4yh6cafuqnhksw5afks4pviwdblsmdunrfu4s4",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3miurixsni5j2"
  },
  "path": "/t/http-tower-hs-a-rust-tower-inspired-middleware-library-for-haskell/13892#post_8",
  "publishedAt": "2026-04-06T22:26:24.000Z",
  "site": "https://discourse.haskell.org",
  "tags": [
    "earlier explanation about why"
  ],
  "textContent": "Very interesting. I’ll keep an eye on this as a way to factor out common patterns from service bindings. It’s frustrating that many service bindings implement retries/logging/etc in an ad-hoc way and a good common idiom for that would help.\n\nBy the way, `(&)` is the conventional name for the `(|>)` operator. I’ve written an earlier explanation about why, but it came first and has much better consistency with the rest of the visual language of Haskell operators.",
  "title": "Http-tower-hs — A Rust Tower-inspired middleware library for Haskell"
}