{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreicq3zbn345eswnxfftifotoz6ccwm5fe2bxiwbnz2m7qshunlwlwq",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3migo646qpmh2"
  },
  "path": "/t/modernizing-haskell-code-without-breaking-backwards-compatibility/13871#post_1",
  "publishedAt": "2026-04-01T11:40:51.000Z",
  "site": "https://discourse.haskell.org",
  "tags": [
    "elderephemera.com",
    "ElderEphemera - Modernizing Haskell Code Without Breaking Backwards..."
  ],
  "textContent": "Haskell has changed a lot in the last quarter-century. Many of the new added features and library changes require breaking backwards compatibility to make full use of, but there are also many that don’t. So I’ve rewritten the Haskell Report’s “Maybe Utilities” (a.k.a. `Data.Maybe`) to demonstrate how to write clean, modern Haskell that’s a drop-in replacement for the original.\n\nelderephemera.com\n\n### ElderEphemera - Modernizing Haskell Code Without Breaking Backwards...",
  "title": "Modernizing Haskell Code Without Breaking Backwards Compatibility"
}