Re:Scaling Erlang Developer Experience at WhatsApp [pdf]
by toast0 on Friday September 11, 2020 @05:43PM
(#24447648)
> Shared, mutable memory access without some form of synchronization is a bug and is always invalid.
That doesn't prevent it from being really easy to write, and sometimes very hard to notice in a lot of languages. In BEAM languages, you can, of course, set up similar bugs through the use of other processes (or ETS), but you have to work harder to do it wrong than to do it right.
That doesn't prevent it from being really easy to write, and sometimes very hard to notice in a lot of languages. In BEAM languages, you can, of course, set up similar bugs through the use of other processes (or ETS), but you have to work harder to do it wrong than to do it right.