Hacker News Reader

i've been writing Haskell GUIs for a few years and mostly stick to react-banana or reflex because wiring up gtk-gi signals manually gets messy fast. The Elm architecture pattern here looks clean on paper but I'm curious how you handle async events from the widget tree without ending up in callback hell. Did you end up wrapping all GI callbacks in a channel that feeds into your update loop?

View on HN

I haven't seen anyone write about wiring FRP systems to traditional GUI toolkits. Do you have a blog?

This is exactly what's done by Relm4 (https://relm4.org/) and vgtk (https://docs.rs/vgtk/latest/vgtk/). It's an interesting idea, but toolkits have a lot of state that's difficult to integrate perfectly with this approach.

Is Haskell in this case just binding a local HTTP port that users then hit with the browser? Or is it like a Tauri/Electron type of thing?

It's a native desktop app, so none of the above.

Reply on news.ycombinator.com