Suture – Supervisor Trees for Go

It would be interesting to see what it takes to get this functionality (at least locally) into Haskell given that there <i>are</i> asynchronous exceptions... even ones with arguably greater safety than their Erlang compatriots.<p>A similar effort is happening with the Cloud Haskell program, but my understanding is that they&#x27;re pouring a lot of effort into transmitting arbitrary Haskell functions over the wire between computers. This is pretty unnecessary for supervision and &quot;Let it Crash&quot;-style error handling alone.

Great article. I especially enjoyed the clear descriptive problem framing and discussion about Erlang processes versus goroutines.

This was interesting simply for the explanation of Erlang systems, but as for the project itself I currently use Supervisor (<a href="http://supervisord.org" rel="nofollow">http:&#x2F;&#x2F;supervisord.org</a>) for this purpose, and I&#x27;ve been pretty happy with it.<p>Any reasons to make the switch?

Why not just use Erlang?

I did something similar in Python, using Redis for the &quot;operating system&quot; and Linux processes. The system managed wide sets of parallel I&#x2F;O operations with second-level latency. Worked great, albeit orders of magnitude slower than something like this. If you keep the supervisor on the same machine, you can do async exceptions via kill.

Any pointers on what blogging setup is being used at jerf.org for writing this post? I found the page pretty tasteful.