From: Phillip Gawlowski <cmdjackryan@...>
Date: 2010-11-10T02:16:52+09:00
Subject: Re: Ruby Perofrmance

On Tue, Nov 9, 2010 at 1:10 PM, Oliver Schad
<spam.entfernen.und.bring.gefaelligst.ein.bier.mit@oschad.de> wrote:
> The winner in speed is always compiled native code. So you have to know
> your requirements.

This may sound facetious, but it isn't:
The fastest code is code that never runs.

In a nutshell, write your code *well*, and keep DRY and YAGNI close to
your heart.

That also means that you should keep around results of calculations
that take a long time around, and try to avoid hitting high-latency
bits and pieces whenever you can ("Do I really *need* an accurate
time? Then why am I accessing an NTP server, anyway?").

Architecture wins, especially if you keep in mind the constrains of
your target system (I wouldn't, ever, use Ruby, Java, or .NET to
program a micro-controller. Conversely, I wouldn't write a CRUD
desktop app in C/C++ these days).

-- 
Phillip Gawlowski

Though the folk I have met,
(Ah, how soon!) they forget
When I've moved on to some other place,
There may be one or two,
When I've played and passed through,
Who'll remember my song or my face.