comment on

RE: Version control
CVS is your friend if you are concerned about controlling version releases. You can use a scripted cvs client to ensure that clients and individual boxes all run the latest and greatest version of your code.

If client access to/modifying source is an issue, how do you handle it for existing csh scripts? If it's not an issue for csh scripts, why is it an issue for the perl equivelent?

If obfuscating source is a big deal, perl has a compiler or you could obfuscate the source.

RE: Speed
If csh scripts are fast enough for your application, I don't see perl's speed being an issue. If speed is a major issue, you can always consider coding speed critical components in C (as xs) and using perl for the rest.

RE: SQL
Perl has DBI. What is he comparing to DBI? Perl DBD drivers provide useful things like statement caching that provides a speed boost for Oracle and other databases.

RE:HTML and C
What is your ex-boss talking about? Writing CGI stuff in C? mod_perl and apache will give you a platform that can execute nearly as fast as C but with less development time/effort.

RE: Libraries/plug-ins
Has your ex-boss ever visited www.cpan.org? In addition to CGI/mod_perl libraries, you can find modules that will reduce the need to write all your own libraries.

RE: Programmer availability
It's pretty difficult to find good programmers in any language, not just perl, csh, or C.

RE: TK
Perl has an interface to TK. It's been around long enough and is popular enough that OReilly has published books on Perl+TK.

Frankly, I think your ex-boss has a bias against perl (or anything different). Much of his post is FUD against perl.

In reply to Re: Rebutting my Perl enthusiasm by em
in thread Rebutting my Perl enthusiasm by el-moe

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl Monk, Perl Meditation
	PerlMonks