3 ms·
> A process is a goofy, unfortunately loaded name for an independent unit of execution. It is not an OS process, and it is not an OS thread. It's such a small
by nailer 11y ago
> A process is a goofy, unfortunately loaded name for an independent unit of execution. It is not an OS process, and it is not an OS thread.
It's such a small thing, but I do get bored of having to explain that unfortunate naming. Now I just say 'actor' or 'Erlang process' then clarify that's not the same as a process, or thread/LWP. It's like how system can mean 'kernel space' (performance tools) or 'service management' (systemd).
- DanielDent 11y agoI think process is a great name. Keep in mind there are architectures where the BEAM VM runs without a traditional OS below it. Before: Physical Machine (x86) + x86 VM + Hypervisor + OS + BEAM After: Physical Machine (x86) + x86 VM + Hypervisor + BEAM Eventually we might get down to: Physical Machine (ARM) + BEAM The hypervisor has domains, the OS has processes, and the BEAM VM also has processes. Why introduce yet another name?
- nailer 11y ago> Keep in mind there are architectures where the BEAM VM runs without a traditional OS below it. That's really interesting - where can I read more? > Why introduce yet another name? I've already explained my own perspective, but I'm happy to disagree.