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).
I believe it is just a wormhole pointing to the original so even if it may look like another body it's just the original being manipulated through the warped spacetime continuum
The real answer btw is no, cloned animals aren't identical to their original, same base traits, but for example in cows spot position will be different
Also unless you can copy their memories, they just won't be the same person.
And then they'd have two different life experiences and would immediately begin to differ.
And we also change every milisecond. How long this process takes? It may seem irrelevant but copy of you 5 seconds ago is not you now. It's your restored back up.
If the transporter takes all the atoms that make up a person, encodes them, beams them somewhere else, and then reassembles them, how can we know that the resulting "person" is the same person who went in?
Huh. Now my confusion about the chicken and the egg debate makes a lot more sense, it seems odd to me that such an easily answered question ended with so much confusion
I'm now realizing it's only a debate with non programmers, I thought it was a mutual ADHD communication thing, now I'm realizing maybe it's just because they learned about inheritance
Imagine if you saw someone who looked exactly like you and mimicked your exact actions, but they were just 3 or 4 feet to the left of you. That's by reference (I think)
Contrasting an exact copy of you that can think for itself and has autonomy, which is by value (I think)