@unbalancedparen @knewter @peregrine @rbondev @jayroh a system designed for messaging where all messages are copies... for starters
@unbalancedparen @knewter @peregrine @rbondev @jayroh a shared heap garbage collector can have similar soft realtime characteristics...
-
-
@unbalancedparen@knewter@peregrine@rbondev@jayroh ...while also reducing the total amount of allocations/garbage... -
@unbalancedparen@knewter@peregrine@rbondev@jayroh BEAM tried this and failed with the shared/hybrid heap experiments
End of conversation
New conversation -
-
-
@bascule@knewter@peregrine@rbondev@jayroh you can have soft realtime with shared heap, but you lose process isolation -
@unbalancedparen@knewter@peregrine@rbondev@jayroh isolation in BEAM is an illusion. If it segvs, it segvs... -
@bascule@knewter@peregrine@rbondev@jayroh :| sure, if the BEAM segvs, it segvs. but if one process crashes it does not propagate -
@unbalancedparen@knewter@peregrine@rbondev@jayroh there's no reason why you can't have similar semantics with a shared heap
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.