in reply to Re^7: Backend diversity for Rakudo
in thread Backend diversity for Rakudo

I don't know. And neither do you. And that is the problem.

Spawning a thread is trivial. Spawning two copies of the run-loop inside two threads is trivial. Had this been done routinely from day one, running two copies of the same code in each run-loop and comparing the results with each other, and with those from a single threaded run of the same test code, reentrancy errors could have been detected and corrected as they occurred.

By leaving concurrency as an afterthought to be bolted on later, the odds are that whole swaths of the the core code will be built on top of reentrancy conflicts that will be neigh impossible to resolve without major rewrites. And given the low priority, bordering on active hostility, towards concurrency, achieving the will to correct such problems is very unlikely.

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.
RIP an inspiration; A true Folk's Guy

Replies are listed 'Best First'.
Re^9: Backend diversity for Rakudo
by chromatic (Archbishop) on Aug 17, 2010 at 21:31 UTC
    I don't know.

    That seems to undercut your assertion that it's too late for Perl 6 or Parrot to do anything sane with concurrency.

    ... given the low priority, bordering on active hostility, towards concurrency...

    Utter nonsense, but well volunteered anyhow.

[reply]

      Selective hearing and denial, combined with a tunnel vision agenda. Pretty much sums it all up.

[reply]

        I'm not impressed by your repeated claims that "Perl 6 hates concurrency and refuses to do anything about it!" and then your repeated refusal to do anything other than hurl abuse and then your repeated citations of the disinterest of Perl 6 developers of listening to you as evidence that they hate concurrency and refuse to do anything about it.

        I think instead that Perl 6 developers (though I only speak for myself) have a disinterest in random abuse.

        I (speaking again only for myself, though I believe the sentiment extends beyond myself) welcome proposals, code, and specific use cases and even actionable criticisms from people with concrete experience working with and designing concurrent systems.

[reply]

In Section Seekers of Perl Wisdom