2 ms·
ferd did a great write-up on how Erlang approaches reliability: https://ferd.ca/the-zen-of-erlang.html https://ferd.ca/the-zen-of-erlang.html It's more about
by nickpsecurity 8y ago
ferd did a great write-up on how Erlang approaches reliability:
https://ferd.ca/the-zen-of-erlang.html https://ferd.ca/the-zen-of-erlang.html
It's more about assuming things will fail by default with good ways of handling it built-in at the language level. A lot of people also find its inventor's thesis enlightening. Here it is:
http://ftp.nsysu.edu.tw/FreeBSD/ports/distfiles/erlang/armstrong_thesis_2003.pdf http://ftp.nsysu.edu.tw/FreeBSD/ports/distfiles/erlang/armst...
And for those concerned, there's also at least one project to write the native functions in a safer language to reduce their bugs a bit:
https://github.com/hansihe/Rustler https://github.com/hansihe/Rustler
- bonesss 8y agoA lot of these concepts have been carried forward to some popular frameworks and languages. Akka (or Akka.Net & Akkling), is a great example. Railway Oriented Programming (https://fsharpforfunandprofit.com/rop/ https://fsharpforfunandprofit.com/rop/), has gained some traction in the .net sphere and, along with F#'s Result<'success, 'failure> type, emphasizes structured and exception-less error handling. It may be a poor mans Erlang, but better than nothing ;)