3 ms·
> All user written code is call-back based, reducing code complexity I think this line deserves further explanation. (I wish people would just post the video o
by SCdF 10y ago
> All user written code is call-back based, reducing code complexity
I think this line deserves further explanation. (I wish people would just post the video of a talk instead of slides, they are often devoid of important context).
- jlouis 10y agoErlang programs are typically structured around OTP-like style. In this style an executing process consists of an "upper" half, written by the user as a module of callback hooks. And a "lower" half which is reused in all components. The lower half usually doesn't "trust" that the upper half is doing things correctly. Furthermore, Erlangs core is functional, so data is by default persistent which makes it harder for code to do "nasty" things to other parts of the code. From a correctness perspective it makes it harder for code to mess up. From a security perspective correct code with hard error constraints is safe, leading to controlled process crashes with no memory corruption. Of course it is no panacea, but it goes a long way toward making systems safe.