in reply to Re^14: Your main event may be another's side-show. (Coro)
in thread Your main event may be another's side-show.

There were no attempts at snide put-downs. I didn't waste any keystrokes on trying to disabuse you of that impression (the couple of times I suspected you had assumed such) because history shows you will see them when they aren't there and won't believe when they are denied and may even interpret the denial as a worse sarcastic insult.

Thanks for mentioning that, though. It makes some of your reactions easier to understand.

Thanks for the repeated insults. You've got a nice theme going. Makes it easier to properly ignore them.

Yes, the first sentence of the previous paragraph was sarcasm. No, none of the rest of it was. Well, the full thread was pretty long so I might've forgotten something. Let me check...

"When you tie yourself to a framework like iThreads" was a quite mild attempt at irony, not what I would call sarcasm.

"have as much fun as you want with that" was not meant completely literally.

In particular, "Perhaps you have little experience with programming with real threads so much of my exposition is foreign to you?" was not sarcasm. I have little knowledge of your particular experience. At any moment, I may remember a few recent snippets that touch on such, for example, a complaint you made about using cooperative-multitasking operating systems. I have no memory of descriptions of you working with real threads. It was just an honest question.

"then it is unfortunate that you missed almost completely the point and have no interest in discussing any of the other 'issues'" was partially an attempt at "turn about" but was qualified with a conditional so was also an honest question and an attempt to redirect the discussion (back).

"If you can't understand that without a piece of code for you to run and so choose to assume that it is overblown raving, I don't really care" was not an attempt at an insult, either. You just now noted that you repeatedly have difficulty understanding me (I think you posed it in the form of an insult to me, again). I don't choose to assume that the difficulty in understanding can be blamed on only one participant in this discussion so me pointing out that you aren't understanding me is not criticizing you, it is me criticizing us both.

Noting that you chose to assume it was overblown raving was noting your assumption of something (I'm not sure what) other than a sincere attempt at discussion on my part. Not particularly helpful and so worth mentioning but not productive to raise a separate debate about. I don't try to drag people, kicking and screaming, into civil discourse if they don't want to do such.

"I don't find scaling such to be even close to as interesting of a problem so have fun with that" was pretty much just honesty. The last few words have style of sarcasm in them but I'm just that way and it wasn't meant as pointed, hard, or biting sarcasm. Just playful language.

Well, that's it. Honestly. Anything else that you took as sarcasm or anything at all that you took as attempts at snide put-downs I disavow any responsibility for such an interpretation.

As to difficulty in understanding, I don't consider your repeating of the equivalent of "despite your excessive verbosity, your descriptions are lacking" to be a sincere attempt at improving the situation. I can't read your mind so if you can't do better at doing your part to improve the success of the discussion then I'm fine with writing you off as "hopeless impedance mismatch; usually a waste of time for me to try to have a discussion with".

But then, we all know the best description of code, is the code itself.

The "code itself" (for any of the cases I'm talking about) is many tens of thousands of lines and so makes for quite a horrid "description", actually. It is nice that you find it extremely easy to make short mock-ups in code that you find adequately convey a complex situation that you are trying to describe. I find quick mock-ups very often end up with the "quick" part being relatively quick but that the "last 10%" (of actually making it work and thus be useful as an example) can take even more than the fabled "90% of the time". So I don't embark on such time sinks for myself much.

And then there are tons of details in working code that can't be "glossed over" and so figuring out what the point of the mock-up was from reading the code is often not an obvious step for me. So I probably wouldn't understand your discussion in the form of code any better than you understand me. C'est la vie.

- tye        

  • Comment on Re^15: Your main event may be another's side-show. (Coro)

Replies are listed 'Best First'.
Re^16: Your main event may be another's side-show. (Coro)
by BrowserUk (Patriarch) on Oct 22, 2010 at 06:11 UTC
    And then there are tons of details in working code that can't be "glossed over" and so figuring out what the point of the mock-up was from reading the code is often not an obvious step for me. So I probably wouldn't understand your discussion in the form of code any better than you understand me.

    I'm sorry, but I simply do not believe that you can't demonstrate your magical "coroutines without cede points" in a few lines of code, without the need to post some humongous lump of proprietary code.

    Which just leaves me thinking I know the real reason you'd rather write at length on distractions, than do so.


    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.