Re: Re: When to use perl

Perl is a great tool. So is Java... Python... COBOL... Each tool has its strength and weakness.

COBOL has no advantages. COBOL needs no advantages.

The politically correct trend towards "the right tool for the job mentality" is getting a bit out of hand. Sure it prevents a few flamefests (and quality discussions about language design), but really, what can Perl/Python/Ruby/Java/ that Java/Ruby/Python/Perl can't? They're so similar it comes down to what your developers already know well, speed/efficiency, and platform support. The four languages I list are in the same category for speed, efficiency, and portability concerns, so it isn't really an issue either. They're all the same slot screwdriver, just different brand names in different colors. Pick the one you find most pretty and are most familiar with.

Comment on Re: Re: When to use perl

Replies are listed 'Best First'.
Re: Re: Re: When to use perl by cciulla (Friar) on May 31, 2003 at 14:45 UTC
Although I wouldn't catagorize "right tool for the job" as "politically correct", you do bring up a valid point. With a caveat. Pick the one you find most pretty and are most familiar with. I concur that when the developer has the latitude to choose how the work is done, then pick the tool that you are most comfortable with. Unless you are your own customer, this doesn't occur often as your customer will have (for good or evil) a standard development platform. Apparently, the OP's boss found that rare customer, and chose perl. The OP has a choice: use perl, beat feet, or suggest that another tool may be in order. Needless to say, the last two are very closely related. On my current assignment, my customer chose WebLogic, Java, and SQL Server. While I am within my rights to use perl to automate some of the more tedious aspects of development, I would be entirely out of line to put any of this into production. If I felt strongly about implementing a solution in some other tool, it is my responsibility to recommend this to my customer. It is equally my responsibility to abide by their decision, or move on. COBOL has no advantages. COBOL needs no advantages. I disagree. While my personal preference is never to look at COBOL again, if my job depends on me dusting off my Stern & Stern, guess what I'll be doing. Bottom line: "Him that pays, says." C²	[reply]
Re^3: When to use perl by adrianh (Chancellor) on May 31, 2003 at 16:16 UTC
COBOL has no advantages. COBOL needs no advantages. When a company has several million lines of working COBOL code that the organisation relies on for daily operations then COBOL has an advantage :-)	[reply]
Re: Re^3: When to use perl by vek (Prior) on May 31, 2003 at 20:03 UTC
I agree with you 100% adrianh. I work for one such company that has about a million lines of legacy COBOL code that is relied apon for daily operations :-) -- vek --	[reply]
Re: Re^3: When to use perl by kutsu (Priest) on Jun 01, 2003 at 00:31 UTC
When I started with my company, continuing to today in fact, all our register programs were written in COBOL, so I programed in COBOL. Saying this, I would love to see these programs redone in C, C++, or almost anything else. "Pain is weakness leaving the body, I find myself in pain everyday" -me	[reply]