News for hackers. Stuff that matters.
Re:The Road to Rust 1.0 by Xorlev on Monday September 15, 2014 @09:59PM (#8322663)
From what I understood, it's a Rust agent communicating protobuf structs over IPC, not embedded into the gem.

In such a case, memory safety and GC is less of an issue.

Re:The Road to Rust 1.0 by bjz_ on Monday September 15, 2014 @10:13PM (#8322696)
Memory safety is still good for long term code maintenance and refactorability. wycats also mentions that these processes are reasonably long lived - memory leaks can become a big problem over time if you are not careful. These can be mostly purged by static analysis and Valgrind, but are still a headache to deal with. I would also add that Rust is much easier to hack on safely if you don't have a great deal of prior systems programming experience.
Re:The Road to Rust 1.0 by dbaupp on Monday September 15, 2014 @10:34PM (#8322744)
I believe there is a Rust library embedded in the gem to serialize and communicate with the outside agent (IIRC, this is actually the most important part to be in Rust, it needs to be efficient to avoid interfering with the normal operation of the main program as much as possible).
Re:The Road to Rust 1.0 by ben0x539 on Tuesday September 16, 2014 @07:28AM (#8323942)
I've never looked at it too closely, but wycats has talked about how the Ruby code calls Rust code through the FFI and how Skylight doing some special things to make that work especially smoothly by directly calling some internal functions of Rust's failure handling bits, and about how the Rust code crashing shouldn't take down the rails process. That seems to suggest it's not just an IPC thing.