some of the things you said e.g. about why you think ithreads is a strong concept that's just not implemented ideally, were illuminating.

Thank you for noticing. I respect your preference for the process-based model.

I don't agree with you doesn't mean I find your POV unworthy of consideration.

Ditto.

I just wish these posts were not coated with such an unappetising sheen of belligerence.

Believe it or not, I agree with you.

I wish it was possible to express a positive opinion of the iThreads model--or any, counter-the-current-trends, opinion--here, without them getting drowned out by catch-phrase contentions and bumper-sticker labelling by the usual suspects.

With today's tenancy for short attention spans and sound-bite evangelism, unless you can persuade or cajole the sound-bite slingers to expand them into something that can be countered on a blow-by-blow basis, then all that gets remembered is the sound-bite. Which is why those who are entirely aware of the technical limitations and outright inaccuracies of their sound-bites choose to hide behind them.

The point of this meditation is to point a real-time example of how, yesterday's FUD becomes today's de-facto understanding.

As for your implication that I am trying to censor or limit the things you should talk about: Please! Enough with the paranoia already!

No paranoia. Just counter argument through reductio ad absurdum.

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

In reply to Re^4: Why it is important to counter FUD. by BrowserUk
in thread Why it is important to counter FUD. by BrowserUk

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.