I hope you don't object to me continuing this discussion? I find debate the best way for me to clarify my own views and opinions--and you debate well.

That said, I'm going to be lazy here and summarise(*) your post above.

(* I mean 'precisé', but I'm unsure of the correct spelling. I know that last grapheme is incorrect, but I don't know how to produce (what I think) is the correct one.)

I'll summarise it as: "Threading is hard, especially for beginners. It will require you to think differently and use different tools. You may find it easier not to try."

That is an unfair simplification of the position you have expressed in the preceding posts. But not by much.

Programmers have an inherent bias that leads them to believe and express that what they do is hard. It makes sense. It is good for business, and good for salaries. But ostensibly, relative to other technical fields, it is entirely wrong. Or at least, overstated.

Learning to drive is a radical departure from anything you are likely to have done before you do it. It doesn't just require hand-eye coordination, but rather hand-eye-foot-brain coordination. But more importantly, it requires anticipation of the actions and reactions of others. Whilst some other activities--sports; computer games etc--exhibit similar requirements, the difference is that mistakes when driving are not just sometimes lethal, but frequently so.

By contrast, programming is essentially benign. Barring the extremes--nuclear power plants; weapon systems; medical equipment--programming errors are seldom lethal. And even in those extreme cases where they can be, they can in most cases be mitigated by proper and conscientious testing.

The point I'm trying to make is that everyone has to start somewhere. And regardless of the complexities of the task undertaken by a programmer, there is always a learning curve involved. But unlike many other fields of endeavour, programmers have the inherent benefit of being able to test the effects of their skills, prior to putting them into potentially lethal practice.

Sure, threads are different. Threading can be hard. But neither fact should be lauded as a reason to preclude anyone from trying to acquire the requisite skills.


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.

In reply to Re^6: Multithreading, how to? by BrowserUk
in thread Multithreading, how to? by iSina

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.