comment on

Thanks for all your great work on Perl, some of us really appreciate it.

And so do I. Which is why he has always commanded my utmost respect for his willingness to interact with us mere mortals in this forum.

Even when he has not responded in kind. Even in this thread, I congratulated him for his continued, valued, expert contributions.

But he didn't create the code in question. I'm not questioning him or his frankly amazing, ongoing contributions to Perl; but rather the code produced by a third party, that for some reason he feels the need to defend.

... inject facts into this thread. The irony ...

Irony indeed. From the pop-up expert who has an overall posting rate of 0.12 posts per day; but who's contribution rate for the last 3 years has been 0.00737 posts/day.

"Facts" require evidence; none of which has been provided. Look up the word "hearsay". Dave_the_M has my utmost respect; but not hero worship.

If he treated me with the same respect I've afforded him; this subthread would not exist.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'

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". The enemy of (IT) success is complexity.

In the absence of evidence, opinion is indistinguishable from prejudice.

In reply to Re^16: Our perl/xs/c app is 30% slower with 64bit 5.24.0, than with 32bit 5.8.9. Why? by BrowserUk
in thread Our perl/xs/c app is 30% slower with 64bit 5.24.0, than with 32bit 5.8.9. Why? by Anonymous Monk

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


There's more than one way to do things
	PerlMonks