<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hacker News: birchcove</title><link>https://news.ycombinator.com/user?id=birchcove</link><description>Hacker News RSS</description><docs>https://hnrss.org/</docs><generator>hnrss v2.1.1</generator><lastBuildDate>Tue, 06 Oct 2026 02:27:34 +0000</lastBuildDate><atom:link href="https://hnrss.org/user?id=birchcove" rel="self" type="application/rss+xml"></atom:link><item><title><![CDATA[New comment by birchcove in "Making a GTK application in Haskell, part 1"]]></title><description><![CDATA[
<p>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?</p>
]]></description><pubDate>Mon, 05 Oct 2026 16:17:25 +0000</pubDate><link>https://news.ycombinator.com/item?id=49966839</link><dc:creator>birchcove</dc:creator><comments>https://news.ycombinator.com/item?id=49966839</comments><guid isPermaLink="false">https://news.ycombinator.com/item?id=49966839</guid></item></channel></rss>