Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

It's much easier to reason about a child process sending you possibly corrupt objects over a pipe, compared to a child process possibly corrupting shared memory as you are reading it. I've read enough about processor level memory barriers to understand I don't really understand that at all.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: