C/C# fork vs thread vs bg worker?

Question

I learnt about fork() and execv() in c and many other system calls and still some things aren't that clear to me.

A while ago I wrote a C# program where I used threads to make my program update the database without making the UI freeze. are processes different that C threads, and are they different than C# threads or background workers.

I am totally lost in this. why we need fork() when that's what thread does.

https://stackoverflow.com/questions/17736407/c-sharp-equivalent-to-fork-exec — Franck Magazine, Apr 25 '21 at 19:16
If you are using .NET you should be using [async](https://learn.microsoft.com/en-us/dotnet/csharp/async) not `fork` not threads. — Dour High Arch, Apr 25 '21 at 19:33

score 1 · Answer 1 · answered Apr 25 '21 at 20:10

why we need fork() when that's what thread does.

fork() and threads solve different problems.

fork() is an older parallel programming paradigm that spawns child processes that inherit memory from the parent, but don't share it like threads do (writes to the memory only change the memory in one process, not the others). While this model of parallel programming is largely superseded by threads, it is still useful when isolation is required.

In addition to the above, fork() can be used with exec() to start different executables and build pipelines between them. This use of fork() is still relevant and is how Unix shells implement complex commands like sort | uniq | wc -l.

C/C# fork vs thread vs bg worker?

1 Answers1