It’s more efficient for memory until you start working with different data. Threads also rely on the same syscall on Linux, clone(2), but they don’t share the entire context by default, so they’re more lightweight. It is recommended to use pthreads(3) API instead of fork(2).
raubarno
A devastated Software Systems student, libre software promoter. Sometimes I draw pixel art. Very fond of classical Computer Science and Touhou project.
- 1 Post
- 15 Comments
If you fork a process, then it’s the two separate processes but sharing the same memory with copy-on-write mapping.
Literally me 7 hours ago
I wanna watch Mr Bean now
Saved your comment. I remember, there were also some for displaying/jumping between the frames of call stack. Okay, thanks.
Uhh, I’m too lazy to learn all the GDB commands.
raubarno@lemmy.mlto Programmer Humor@lemmy.ml•If Programming Languages Were Games (Comic)181·2 years agoHaskell isn’t really that hard to learn. It’s just changing the paradigm, that takes a mind shift for the first two weeks, maybe a month.
I don’t play games that much to make such comparisons, though.
C*
, the language of null-dereferences
(X-Files music starts playing)
- Part 1: What Lies Behind the Undefined Behaviour in C
- Part 2: Mystical Appearances of CPU Cache Invalidation
- Part 3: Secret Council of the Church of Emacs
- Part 4: Strange Encounters with Supernatural Software Bugs
OMG I wonder how old some of these SPARC machines are…
“And in the next episode, we are going to build a self-driving car from scratch.”
Haha, I want to see a race condition going on with real matter.