The old "we want to be able to call the vendor" line is standard CTO bull for "I don't understand Perl and thus I fear it." Anyone who has actually called a vendor for support, and has compared the speed and quality of the response to what you get for free on the dozens of Perl support sites, lists, newsgroups, and IRC channels knows that vendor support is a joke.
The C language has no support, but C compilers do. SQL has no support, but Oracle does. I don't think you'll win the argument that way.
Demonstrating the quality of support Perl has and the support available for purchase from ActiveState would be enough to convince any reasonable person. However, support is almost certainly an excuse, rather than the real reason, so winning that argument may be useless. Of course, if you can get your employer to give some money to ActiveState, by all means do it. ActiveState pays people to improve Perl for us, so it would be nice to keep them in business.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.