I found a nice article online titled How Perl can Avoid Java's Worst Web Messes that, although does not discuss the subject of this post directly, contains a section that I think pretty much sums up how to solve the supposed weakening of Perl in favor of Python's offerings dilemma. I'll copy the bulleted list here and make a few edits:

• Avoid the overcomplexity of projects by emphasizing the flexibility and simplicity of the [ language/module/feature/etc. For me, I would emphasize these in the reverse order. That is, key in on simplicity first and flexibility second. My take on a lot of programmers nowadays is that they want to be spoon fed the right way to do things. They will take a simple example over a lengthy discussion of multiple ways to accomplish something. ]
• Write better documentation. [ You are not going to win without this, which is one of the reasons for my reposting these bullet points. Making good documentation is a collaborative effort. You will have to either guide module authors to write more clearly or rewrite the documetation for clarity/brevity yourself.]
• When the best way to do something changes, deprecate old documentation and point to the new approach. [ I covered this in the last bullet point, but I think the key is to take up the pen and combat outdated/inaccurate information whenever possible. For example, there is this guy who created a website to catch U.S. military veteran imposters. I saw a television news story where even some branches of the military were using the site to weed out phonies. You never know what one person can do to change the world. ]
• Emphasize simplicity. Make the default a good way to do most things. Provide comprehensive tutorials which explain the entire system using that effective default. [ Frankly, I don't know what this means but it sounds good. ]
• Provide smaller upgrade paths and avoid big-bang incompatible releases which fork documentation and knowledge. [ In other words, think Agile. ]
• Unify where possible. [ In order to do this you need to create synergies between people who are working on different, but complimentary modules/documentation/projects/etc. Work on your people skills for this because you will need them. Don't forget that you will attract more bees with honey than vinegar. ]

In all, if you apply these principles collaboratively with others who think/feel/act similarly you can turn around virtually anything including some perceived trend toward a weakened position. I think what people want to see most of all is activity that produces results that will benefit them in their work and/or lives. When that activity is clear and the benefits are easy to grasp people will naturally gravitate toward it. When it is not the attention quickly moves to the path of least resistance, which normally means a competitor.

---

---

• 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.