It was a sincere apology. I consciously tried to err on the side of assuming that I had caused more hurt. I'm rather loathe to say more as I suspect some of it will be taken badly. However, I will try one more time to soothe things a little by explaining. I'm not trying to claim that I didn't err, just to better explain my position and lack of malace toward you.

I certainly wasn't trying to abandon the chatterbox discussion. The discussion went fairly slowly and to my mind it was finished before I started writing this. I was certainly around and don't recall you asking where I'd gone or why I wasn't responding to your attempts to continue the conversation. I'm sorry if you felt I had cut the conversation off.

I didn't have anything more to add in the discussion between you and me. The node I posted was not a continuation of that discussion nor was it directed primarilly at you. I finally felt like I understood what I had previously misunderstood about your node. You said that you might be able to post the before/after code and I was looking forward to that.

If and when that code appears, I will try to find the time to address a remaining point with you that I didn't feel I could address well (yet) in our chatterbox conversation nor in my original node. Namely, what the real source of the 6-fold speed up was. If others resolve that question, then I'll be happy to read about it and otherwise stay out of it.

My original node was primarilly addressing those who read your node. I explained how I had got the wrong impression from your node and that I think that some others did as well. And I explained that some jumped to what I consider to be impossible conclusions based on those impressions. So I conveyed that you had said that giving that impression was not intentional (and I did not try to attribute any fault to you, but stated that I understand how people could get that impression) and addressed why I consider those conclusions impossible.

I was talking about what you had written and what you had said in the chatter box and so I was only trying to be polite in addressing you by handle and doing the traditional linking to it.

I was not trying to imply anything with "finding the strength" other than that I assumed it might well "be too frustrating a task", as you say.

If you have some specific constructive suggestions on how I could have better presented things, then I will certainly listen to them and try to take them to heart. I'm sure there are many ways that I could have done a better job.

I will make one attempt at a concrete, constructive suggestion to you. Although I certainly don't know you well, I get the impression that you might benefit from making an effort to worry less about whether words, actions, or feeling are directed at you personally. Perhaps a paraphrase of your worthy sig line would be appropriate:

Examine what is said, not who it is said to.

I hope you can take this suggestion in the spirit of kindness that I am offering it. Emotion is very difficult to convey and very easy to misinterpret in on-line communication. My suggestion may be way off base. If so, I apologize. It is honestly just an attempt to be helpful.

Sincere best wishes and kind regard,

                - tye

In reply to Re^6: Micro optimisations can pay off, and needn't be a maintenance problem (I don't believe it) by tye
in thread Micro optimisations can pay off, and needn't be a maintenance problem 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.