[samsquire]

This is interesting, thank you.

I really should learn from BEAM and the OTP and learn Erlang. I get the feeling it's super robust and reliable and low maintenance. I wrote a userspace multithreaded scheduler which distributes N lightweight threads to M kernel threads.

https://github.com/samsquire/preemptible-thread

I recently wrote a JIT compiler and got lazy compilation of machine code working and I'm nowhere near beginning optimisation

https://github.com/samsquire/compiler

How do you write robust software, that doesn't crash when something unexpected goes on?

I looked at sozo https://github.com/sozu-proxy/sozu

and I'm thinking how to create something that just stays up and running regardless.

[fredrikholm]

> I get the feeling it's super robust and reliable and low maintenance

The patterns defined by OTP are a work of art and tremendously rewarding. I've yet to use any other system/runtime that elegantly solves the amount of issues that come up when writing these type of systems up front.

The BEAM is a work of art. Nothing comes close.

[mst]

OTP itself is very definitely worth learning about even if you aren't using it directly.

Reading up on the Erlang GC was fun.

So was reading Kernel.ex (Elixir's bootstrap file)