“Mostly functional” programming does not work (2014)

Re:“Mostly functional” programming does not work (2014) by hueving on Monday June 22, 2015 @08:46AM (#9757851)

What? The only possible way that constraint could be satisfied (working under any hardware failure) would be if erlang didn't let you write any programs that did anything.

[ Parent | on HN ]

Re:“Mostly functional” programming does not work (2014) by thyrsus on Monday June 22, 2015 @09:39AM (#9758193)

The argument is that Erlang (and its OTP environment) gives you the tools to distribute your system in such a manner that hardware failure is observed and that the failed portion of the system is restarted elsewhere. The granularity provided is better than most STONITH models. It provides a lot of help, but one still needs to make an effort to assure that, e.g., merchandise is not sent unless an invoice is generated.

STONITH: https://en.wikipedia.org/wiki/STONITH

[ Parent | on HN ]

Re:“Mostly functional” programming does not work (2014) by fnordsensei on Monday June 22, 2015 @08:49AM (#9757874)

Excuse the aside, but this reminds me of this old Bash quote:

  <FreeFrag> The most secure computer in the world is 
             one not connected to the internet. 
  <FreeFrag> Thats why I recommend Telstra ADSL.

Also, agreed. Some elaboration on that point would be most welcome.

[ Parent | on HN ]

Re:“Mostly functional” programming does not work (2014) by TazeTSchnitzel on Monday June 22, 2015 @09:03AM (#9757959)

http://bash.org/?168859

[ Parent | on HN ]