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

Go already implements many of these ideas. There's os/exec (and syscall.ForkExec), and io/fs (albeit it's a family of interfaces, rather than a descriptor you could pass between processes).

It had to ban forking, because of the guarantees made by the runtime (and all the "weird" OSs it runs on, like Windows). The API is clean and easy to work with, but don't look at the implementation ;)

I'm curious what would "UNIX v3" look like today, if made by the same teams that did UNIX, and then P9/Inferno/Go.



Yes being able to seamlessly swap out the implementation of library functions is a crucial way to justify this sort of work on a shorter timescale.

I'm very glad that many such libraries already have process creation interfaces that possible, and in fact easier, to implement with this approach.




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

Search: