> cherry-picking on that post,

Yes you are.

> I disagree with the "because". I find it rather easy to select the features I like,

Perl has the reputation of the write-only-language which becomes unmaintainable by a team.

This could be related to people "selecting the features they like".

A team leader in application development is interested to have a common coding guideline, an employer to easily find new team members or at least easily train a newbie.

I daresay pretty much everything which makes Perl a great language for short scripts or as interactive shell is discouraged in PBP.

This is a highly schizophrenic situation, because people reading the perldocs have to keep all parallel realities in mind.

The even bigger paradox is that many Perl haters have no problem praising bash and Java in the same phrase.

My point is that this could be solved by readjusting the perspective, either by labeling or maybe enforced by pragmas.

This plus a translation program which helps to translate the first to the later by walking the op-tree.

B::Deparse does already most of the job, like offering to translate special vars to use english variants and an opinionated indentation.

You can't really use Python as a bash replacement and you can't really scale easily to a big application with bash.

Perl can ... an this should be a central message in the way we are selling it.

For instance instead of apologizing for special vars, we would say:

Look they are very handy in "Perl-shell" and not meant to be used in this form in "Perl-app", why don't you "use anal"* anyway?

I hope my point is clearer now.

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery FootballPerl is like chess, only without the dice

*) "anal" in the sense of super-strict

In reply to Re^8: The Future of Perl 5 by LanX
in thread The Future of Perl 5 by Laurent_R

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.