Clear questions and runnable code
get the best and fastest answer
Re: A Porting Horror Storyby Necos (Friar)
|on Apr 09, 2002 at 23:29 UTC||Need Help??|
Whenever I hear these kinds of stories, I think to myself: "I'm glad I don't have to deal with that madness." When I code utilities in Perl, I code them for the task at hand, leaving room for improvement (read: expansion). This is, from what I understand, typical software engineering. If not, it is definitely a good habit.
Here, I grin at the fact that I work for a high school, instead of some PHB-type company. We don't have money to hire 9 million Java programmers, so we code our utilities in what can be done the fastest: Perl. That's why people like myself advocate the use of Perl. It's easy to learn (read: low learning curve) and get something very simple started. It's possible to extend code to be OS-specific if the need should arise. Also, it's one of the few languages (that I know of) that allows for the use of modules. This saves me a lot of time. I can just import a module into my program and start writing.
I don't advocate the use of Perl because I'm some hardnosed Perl hacker. I advocate the use of Perl because it gets the job done, plain and simple. It may not be the fastest thing since C, but that's fine. If I was really worried about speed at that level, my machines would not be running Windows.
In short... Use the language that does what you want when you want and makes it easy for you. Perl is my sword, and I try to use it properly. Until I reach the level of Perl hacker, I'll still train to better my skills.
Theodore Charles III
Los Angeles Senior High
4650 W. Olympic Blvd.
Los Angeles, CA 90019
323-937-3210 ext. 224