News for hackers. Stuff that matters.
Re:Servo Continues Pushing Forward by Manishearth on Friday May 01, 2015 @03:08PM (#9473800)
I think he was talking about Firefox.

FWIW in Servo when talking of multiprocess stuff we colloquially call it "Electrolysis". I think Patrick has some work in progress on this. It's not as much work as the Firefox e10s (we already use threads and channels for everything), but I think there is some (relatively) minor work to be done.

Re:Servo Continues Pushing Forward by zobzu on Friday May 01, 2015 @07:08PM (#9475073)
how do you handle component sandboxing in Servo compared to firefox e10s? (firefox being child process sandbox, ipc to parent, and things being a little "unperfect" in the separation)
Re:Servo Continues Pushing Forward by pcwalton on Friday May 01, 2015 @09:03PM (#9475430)
The plan is to use gaol [1] for sandboxing. For IPC, we want to send Rust objects serialized via serde [2] over native OS IPC pipes (AF_UNIX sockets on Unix).

[1]: https://github.com/pcwalton/gaol

[2]: https://github.com/serde-rs/serde

Re:Servo Continues Pushing Forward by zobzu on Saturday May 02, 2015 @03:40AM (#9476251)
that looks nice i hope the separation between processes themselves will be nicer than firefox (or even chrome) since its "from scratch" :)

(ie that it wont be remoting everything and only protect the system from escaping a child - makes sense in firefox/chrome, less with rust being the compiler i guess)

I suspect that if servo doesnt try to be an OS like firefox/chrome do, a whole process sandbox may even be fine enough. But if it does.. :)