One of the important things for a 'real' language is a slick GUI-based debugger. I demonstrate ptkdb to show a decent GUI and a great debugger. I have often squelched perl criticism by demonstrating ptkdb.

The primary critique of perl is actually economic. The idea that best-in-class tools are open-source scares many people. The feasibility of open-source implies that someone could destroy a closed-source business with a competetive open-source program. Many people would like to deny that this is possible or desirable.

These same people are often afraid of non-perl open-source tools such as Linux. Such people can sometimes be reassured by telling them that you can buy support for these tools from a reputable support organization. Then they get to think, "Well, our world-class support organization will prevent an open-source upstart from knocking us off."

Often perl source code is hidden on a web server, where people can get the benefits of running the program without having access to the source code. If your business model is "I write source code and sell the executable," you are likely to think "perl is a web-server language."

I think that perl is an anomaly in the software world because it is clean, fast, and cheap. As such, it violates people's expectations. If you agree with me and you want be a perl advocate, consider that this anomaly may require extra explanation.

I like explain the benefits of perl using the FURPS model:
Functionality
Usability
Reliability
Performance
Supportability
By running down this list and showing how perl stacks up, you can make a good case.

It should work perfectly the first time! - toma

---

---

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