comment on

I don't see one Java application that doesn't ship with it's own JDK, I don't see why doing the same with Perl wouldn't be benificial to an applications stability, ease of migration, and maintenance.

To resolve issues on development servers here I keep the systems perl separate from the users. I install various Perl flavors beneath /home/perl. (i.e /home/perl/5.6.0/bin/perl, etc)This makes management cleaner for both the sysadmins and the developers. Now that Sun is maintaining it's own Perl distribution (as of 2.8) I don't want to find some patch that plays havoc on the dev enviornments.

Also this argument reminds be of an a coder's complaint I heard recently "The only problem with developing user interfaces is the user".

But ya know Joe, There's more than one way to do it and there's nothing you can do about it :)

coreolyn

In reply to Re: Why I hate Perl (discussion) by coreolyn
in thread Why I hate Perl (discussion) by deprecated

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.


Your skill will accomplish what the force of many cannot
	PerlMonks