{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreihq3uxx6wuubxavw2gvjednfcrpgvoppdenmt4vxddqyrxt3uy3zy",
    "uri": "at://did:plc:pi6woz4d47bkuws673w2il2r/app.bsky.feed.post/3mjiynlvdgd72"
  },
  "path": "/t/ann-rivulet-window-manager/13921?page=2#post_32",
  "publishedAt": "2026-04-15T03:24:16.000Z",
  "site": "https://discourse.haskell.org",
  "tags": [
    "my own personal River window manager",
    "@Kleidukos"
  ],
  "textContent": "Crdr:\n\n> Calling River and wayland functions using FFI works well for my own personal River window manager.\n\nWow! I am genuinely amazed by just how many people have been led to writing a Haskell WM by River. This is incredible! I 100% agree in trying to natively implement the Wayland-wire protocol. The callbacks suck. As I mentioned in the 1st post in this thread, there was some effort with a `wayland-wire` package almost a decade ago. I think we could implement this part of things fairly quickly (or fork & update `wayland-wire` to be modern and current) and get moving on a more dedicated event-stream style thing.\n\nI think there’s definitely enough interest in Wayland Haskell judging by the reactions to this post to form some sort of working group. @Kleidukos what do you think? I’d be happy to lead an effort like that.",
  "title": "[ANN] Rivulet Window Manager"
}