News for hackers. Stuff that matters.
Re:A fork() in the road by zzzcpan on Wednesday April 10, 2019 @09:32AM (#19624430)
> but now you have to establish some form of IPC

Shared memory for threads is a form of IPC too, except one where it's very easy to make a mistake, introduce concurrency bugs.

> I also certainly cannot see any sensible argument for threading being harder than fork()

You should read a paper or two on concurrency bugs. Including on those using explicit but shared communication channels, like CSP does.

Re:A fork() in the road by the_why_of_y on Wednesday April 10, 2019 @04:43PM (#19628589)
Concurrency bugs can be eliminated with state of the art static analysis (see Rust, Pony) - with the exception of deadlocks, which you can easily introduce with multiple processes as well.

http://blog.rust-lang.org/2015/04/10/Fearless-Concurrency.ht...