in reply to Re: Why it is important to counter FUD.
in thread Why it is important to counter FUD.

It's a little more complicated than that, but it is understandable that you aren't interested in the detail. But you do have the choice of simply not reading them.

However, if you find that unacceptable, perhaps you could post a list of subjects that are important to you, to which I should restrict myself?

What's more, if you can get a consensus--let's be generous and say, 1% of the active membership--on what those subjects should be, I'll be so bound.

  • Comment on Re^2: Why it is important to counter FUD.

Replies are listed 'Best First'.
Re^3: Why it is important to counter FUD.
by tirwhan (Abbot) on Oct 28, 2010 at 10:09 UTC
    that you aren't interested in the detail

    As it happens, I am somewhat interested in the issues that are discussed. Concurrency is an important element of programming and discussions about the possibilities of various concurrency models can be enlightening. While I remain securely in the camp that favours a process-based model, it never hurts to hear a differing view, and 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. So thanks for that. And YMMV in these things, always. Just because I don't agree with you doesn't mean I find your POV unworthy of consideration.

    I just wish these posts were not coated with such an unappetising sheen of belligerence. And, though you may be surprised to hear that, I perceive most of the antagonism originating with you (this perception, naturally, is mine alone and I make no claims that it may be shared by others). Which makes it harder and less pleasant to dig through the threads in search of actual information hidden within the barbed comments.

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


    All dogma is stupid.
[reply]
[d/l]
      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.
[reply]
        I wish it was possible to express a positive opinion of the iThreads model...without...

        If this is really your goal, IMO the tactic you chose is highly ineffective and probably counterproductive. Personal attacks on the "soundbiters" you describe (if they even exist, of which I am doubtful) only reduce you to the same level and alienate readers (well, me, at least). Uncalled-for aggressiveness is not a good way to persuade others in a technical discussion. Subsequently hiding behind the straw-man of "they're bad, so I have to be bad too" is downright offputting.

        ...persuade or cajole...

        Please do, it's the bullying I frown upon.

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

        How does one new posters opinion become "de-facto understanding"? And if that was really the point, what is the passive-aggressive "I hope you guys are proud" supposed to do, except alienate further?

        No paranoia. Just counter argument

        To an argument I never made, and which could only be thought to have been there if you looked at my post from the worst possible angle and ignored any exchanges we've had in the past. Paranoia.

        Anyway, this discussion is increasingly meta and I am really not in the position to tell you how to behave (nor would I at all wish to be). Objection raised, do with it what you will.


        All dogma is stupid.
[reply]
[d/l]
        Just being curious - how exactly do you counter Re^10: Why Coro?? That node is a bit heated and perhaps it is difficult to answer it calmly - but qualifying it as monstrous only adds rhetorics and increases the heat. If your goal was to counter the claims - then please do that.
[reply]

In Section Meditations