News for hackers. Stuff that matters.
Re:Errors are values by TheHydroImpulse on Tuesday January 13, 2015 @06:45PM (#8883367)
There are many more areas where you simply cannot abort the process on any error that has been triggered. Erlang, being in the niche of network software, can get away with this because you can have mechanism that monitor the process and it's not the end of the world if one process goes down.

Imagine if your Browser crashed every time it hit an error, like a network connection issue, writing to a file, etc...! That just wouldn't be tolerated by consumers of the software.

Re:Errors are values by fenollp on Wednesday January 14, 2015 @03:53AM (#8885059)
Eh. The point is to not handle things you don't need to. There is of course a point in handling special cases (like the ones you cited). But compare Erlang's declarative & to-the-point style with Go's `…,err = …; err != nil` and you will quickly realise how much defensive programming sucks to read.