Re^4: threads->create hangs (vs fork)

So Perl boldly went and implemented (interpreter-based) threads (i.e. without OS support),

That is completely wrong.

Perl's iThreads are essentially thin wrappers over OS (kernel) threads:

pthreads on *nix;
Windows threads on Windows.

The term "interpreter threads", simply means that each kernel thread runs a separate instance of the Perl interpreter. In this way, each thread runs in its own distinct memory; despite that all of their memory is part of the same single process.

Equally, the rest of your post is a total misunderstanding of the implementation; and a complete misreading of the actual history.

Please refrain from further comment on a subject you clearly have nothing useful to contribute to.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.

"Science is about questioning the status quo. Questioning authority". I knew I was on the right track :)

In the absence of evidence, opinion is indistinguishable from prejudice.

I'm with torvalds on this Agile (and TDD) debunked I told'em LLVM was the way to go. But did they listen!

Comment on Re^4: threads->create hangs (vs fork)