comment on

I think we need better installation processes for both web apps (including mod_perl apps) and other apps, where better = easy for not especially technical people to use.

And where possible, we should, politely, and with specific technical points, call others on their BS about Perl (like I'm doing here where a Python programmer smugly pronounced he recreated Quantum::Superpositions in 100 lines of code... apparently without even realizing that he left out the hardest part.)

Heh. I was just going to take my own advice and leave a comment on some annoying inaccuracies in a PHP vs. Perl weblog entry by a PHPer (which is one of Google's top ten responses for 'PHP vs Perl'), but the site's gone 404 (the link's via the Wayback Machine.) That's a damn shame.

And, of course, we need Perl 6, which cleans up a lot of Perl 5's syntax, gotchas, and, frankly, lame OOP support.

In reply to Re^3: Another prediction of Perl's demise by Zed_Lopez
in thread Another prediction of Perl's demise by bradcathey

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.


Do you know where your variables are?
	PerlMonks