2 ms·
It makes sense, really; C code can really mess with managed systems like that, and by the sounds of it, Erlang deals with it gracefully. Unfortunately, the JVM
by pmjordan 18y ago
It makes sense, really; C code can really mess with managed systems like that, and by the sounds of it, Erlang deals with it gracefully. Unfortunately, the JVM feels a little too monolithic for my liking with regard to processes; it's more unixy than .NET, certainly, and I guess that's the price you pay for a VM that sophisticated.
- jmtulloss 18y agoI wonder if it would be more practical in .NET. They have this idea of Application Domains that I've never needed to fully understand, so never have. Perhaps you could hack that into a Erlang style process model?
- davidw 18y agoThe key point is really this: if you call out to some C function, FoobarFunc(), you simply have no guarantees that it won't sit there in a while(1) { fiddlefaddle() } loop. Since Erlang "processes" are all part of the same OS process, that would kill the whole system dead. So you really need to offload things into their own contained little world, which in this case means a real, Unix process, or at the very least a thread.