if you're going to provide the unix fork() via HLL APIs at all, you need to provide something similar to all platforms.

Why?

The perl 5 Win32 fork emulation is all but unusable. But worse, the result of its presence is that iThreading is close to unusable on every platform. It is, as of the last revision of threads, impossible to start a thread without everything that has already been loaded getting cloned. Need it or not.

That means that starting a thread is slow; and each thread started is far heavier than it needs to be.

You, and the PPD seem to be missing the fact that at the parrot level, everything is shared. Shared everything or shared nothing are execution models imposed upon the HLLs by the parrot runtime and the language implementations.

Let's face it. This is a pointless discussion.

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".
In the absence of evidence, opinion is indistinguishable from prejudice.
"Too many [] have been sedated by an oppressive environment of political correctness and risk aversion."

In reply to Re^6: Slow evolution of Perl = Perl is a closed Word (NQP, parrot concurrency == Oh dear.) by BrowserUk
in thread Slow evolution of Perl = Perl is a closed Word by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.