DIY Mission Control in

I knew all those "launchMissiles :: IO ()" examples will come in handy one day!

Having fiddled with a new FRP wrapper[1] for and *not* using Events/Behaviors/Dynamic in fullest it kinda dawned on me how composition in The Elm Architecture (that I kinda liked) is 1) different 2) related and 3) awkward.

More practice is needed though.


`Map.fromList` considered harmful.

And other funny functions that silently discard data.

Quick morning coffee and I've finally got myself a DNS server bridge to GNS (via REST service, direct bindings being WIP).

It works as a system-wide resolver, having a fallback delegation, but the damn browsers are still refuse to use it for good. Too much smarts, caching and "security" levels piled on top of each other.

I absolutely love interactive output on the site and now want to implement this for all my packages.

> Parsec: “try a <|> b” considered harmful
> tl;dr The scope of backtracking try should be minimized, usually by placing it inside the definition of a parser.

Gory details:

Two things fill the mind with ever new and increasing admiration and awe, the more often and steadily we reflect upon them: storing providence[1] in your types and instances[2] for `Data.Tree.View`.


Mu (forall a. (f a -> a) -> a)
Nu :: (a -> f a) -> a -> Nu f
Pure a | Free (f (Free f a))
... these a few of my favorite Fix

Show more

l'empathie mécanique's choices:


Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!