On Mon, Oct 10, 2005 at 01:22:06AM -0700, Charles Stevenson wrote:
> at least in the proof-of-concept stage. What sort of languages
> inspire you? What features do you look for... use frequently.
I'm jumping into this late, but I can't resist tossing in my $0.02.
Languages are designed around paradigms that make a particular task (or
set of tasks) easier than some other reference implementation. They all
have baggage, as well as strengths and weaknesses. Typically, I try to
use the right language for the right task (e.g. the one it was
specifically designed for). When that's not possible, I either make my
best guess, or fall back on whatever feels comfortable for the job (in
my case, usually bash 3.x out of habit).
So, here's a short list for you:
- I use sed as a language for text transformations.
- I use awk for CSV parsing.
- I use perl for complex text-parsing and reporting.
- I use python when I want to pretend I care about OOP.
- I use php for my server-side web coding.
- I use ruby when I make to make a point to the Java bigots at work.
- I use tcl when I want to do floating-point math.
- I use tcl/tk when I want to code up something with a GUI.
- I use expect when I want to automate something interactive.
- I use lua when I want to automate VCS activities with monotone.
Mostly, though, I use bash and various GNU core utilities, since a few
pipes and redirects are usually all that's required for almost any task
I can imagine. After all, even if the *code* isn't as efficient, part of
practical, real-world efficiency is coding in something you know well
and can apply successfully to the problem domain.
--
Re-Interpreting Historic Miracles with SED #141: %s/water/wine/g
_______________________________________________
RLUG mailing list
[email protected]
http://lists.rlug.org/mailman/listinfo/rlug
