Date parsed: 29/12/2007 06:23:58
Date: Sat, 29 Dec 2007 11:23:58 -0500

On Sat, 29 Dec 2007 12:08:27 -0000, Jon Skeet [C# MVP]
<skeet@pobox.com> wrote:

>Richard Heathfield <rjh@see.sig.invalid> wrote:
>
-snip-
>
>I don't think .NET struggles with recursive algorithms. Tail-recursion
>is only used in certain circumstances (depending on the JIT compiler
>and source language, if I remember correctly) but that's unlikely to be
>responsible for the majority of a 60x slowdown. It may have had *some*
>performance impact, but not of the magnitude you saw.
>
>I suspect it's far more likely that your code had some other bottleneck
>(such as using string concatenation instead of a StringBuilder) which
>was due to inexperience rather than anything inherently wrong with the
>framework itself.
>
One of the earlier posts by Mr. Heathfield mentioned the application
used sockets. If performance was an issue that is where I would look
first.
-snip-
>
>> But we did give it the best shot we could without compromising the
>> deadline.
>
A deadline is just an arbitrary date on the calendar chosen by someone
with a to-do list. Unfortunately marking the task as completed is
often more important than properly completing the task.

>Fair enough - but it really doesn't sound like that "best shot" was
>even slightly enough to give you sufficient evidence for your ".NET is
>slow" claim.
>
That seems to be what everyone is trying to point out. Anecdotal
evidence concerning a port of a port's performance is being given too
much value. The is especially true when the first port involved
hacking on socket code.

regards
A.G.