Chris Uppal said:
I'd be interested to know more about why you see that as a good thing.
Most of the time, the low level perspective is not that relevant for
what I do. When needed, though, it is good to be able to think in low
level, non object oriented terms. To not need to create a zillion
objects or abstractions to solve a simple problem.
It is easy to forget that the high level concepts we usually work in
turn into a whole passel of low level instructions. Most of the time,
that low level code is below my radar, and not where I should be
focussing our attention. Once in a while, though, I do need to think in
terms of bytes on the wire, or instructions on the queue.
Put another way: for the vast majority of tasks, the higher level you
think about the problem, the faster it gets solved correctly.
Performance is thus a minor issue. For example, if I round trip to a
database, I have an automatic lag of milliseconds, and shaving
microseconds is probably irrelevant. Thus, when you do find yourself in
one of those cases, it is hard to shift focus to bytes on the wire. Or,
for that matter, to shift focus to "solve the distraction so you can
move on to the meat of the problem."
Perl makes it really easy to bang out a very quick solution to a rather
large set of problems. As the second half of a one liner find command,
it can save me a lot of development time, or hand editing. I would not
be eager to use it for a major problem again, but as one tool among many
to move a major project along, it is not a bad one.
Scott