News for hackers. Stuff that matters.
Re:Fork() without exec() is dangerous in large programs (2016) by perryizgr8 on Tuesday June 14, 2022 @12:28PM (#31741791)
It's only dangerous if you use libraries without fully understanding what they're doing. And most well designed libraries will avoid creating threads, and will do so only when you make it explicit that you want it to happen.

I also find that libraries that absolutely need to make their own threads are better off being their own process. Then you can use proper communication methods to pass data.

Re:Fork() without exec() is dangerous in large programs (2016) by aidenn0 on Tuesday June 14, 2022 @01:17PM (#31742684)
Per TFA, a large fraction of OS X system libraries use threads, so if you're developing for the Macintosh, fork() is already out.