I agree with (2) and (3), and depending on your definition, (4). My company ships a large shrinkwrap enterprise application in Perl as proprietary software; the source is there and visible, but it's certainly not open source according to any common definition of the term.
(1) might or might not be a problem; I don't really know enough about the problem domain.
After working on this application (about 100KLOC depending on how you count) for the last year and a half, I think my answer is that applications for which correctness is a requirement probably shouldn't use Perl. Most other languages (Python, C, FORTH, assembly, perhaps Java or Ada or Eiffel) are much less likely to hide subtle bugs in apparently-working code. Of these, Python would normally be my first choice, since it has the best power-per-line ratio in my experience.
Perl was and is the right choice for our application, though; flexibility is less important for us than correctness and access to libraries.
-- kragen@pobox.com
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.