News for hackers. Stuff that matters.
Re:Ruby Garbage Collection: Still Not Ready for Production by yummyfajitas on Saturday March 29, 2014 @02:27AM (#7491607)
What simplicity/safety does using processes buy you relative to a good threaded runtime (read: JVM/Haskell/Go)?
Re:Ruby Garbage Collection: Still Not Ready for Production by otterley on Saturday March 29, 2014 @03:27PM (#7493574)
Building a good threaded runtime is difficult in the first instance, and even then, shared memory requires special handling (mutexes).

There has been plenty of ink spilled on the subject, but here's a good read: http://msdn.microsoft.com/en-us/magazine/cc163744.aspx

Re:Ruby Garbage Collection: Still Not Ready for Production by yummyfajitas on Saturday March 29, 2014 @10:21PM (#7494876)
Building a JVM is harder than building an RVM. I was asking from the perspective of user code. Shared memory requires mutexes in both threaded and forked code - this is not an advantage of multiple processes. In fact, multiprocess shared memory is generally harder to work with than threaded shared memory.
Re:Ruby Garbage Collection: Still Not Ready for Production by otterley on Monday March 31, 2014 @02:49PM (#7503364)
We're talking about Ruby here, though. MRI threading has concurrency limitations, so processes are better here IMO.

I tend to think out of the box for multiprocess shared memory - Kyoto Cabinet and Redis can be helpful here, to name a few. Even SysV shared memory is pretty easy to use.