News for hackers. Stuff that matters.

A comment on Erlang's not about lightweight processes and message passing. Parent comment

Re:Erlang's not about lightweight processes and message passing by macintux on Friday April 11, 2025 @04:04PM (#43657939)
Worth noting as a disclaimer for people reading this: this is only true so long as external interfaces are not used. As soon as the BEAM calls out to other binaries, you lose that guarantee.
[ Parent | on HN ]
Re:Erlang's not about lightweight processes and message passing by dqv on Friday April 11, 2025 @11:41PM (#43661146)
A disclaimer to the disclaimer is that you should be isolating that binary on dedicated nodes if there are stability concerns. Inter-node communication is trivial on the BEAM and it can be tweaked in the future when the scale of the system calls for it.
[ Parent | on HN ]
Re:Erlang's not about lightweight processes and message passing by franticgecko3 on Saturday April 12, 2025 @01:15AM (#43661558)
If you write an Erlang function in C you can actually call a function that lets the scheduler know you are willing to yield.
[ Parent | on HN ]