One, though not mentioned, your Perl products must have used extensive logging and transaction control, in addition to secure file transfers.
Second, the big problem with Perl in my opinion are the types of texts published about it. There are reams of books on the Perl language but very few about Perl as the language for architecting complex systems.
In contrast, look at the catalog for Addison-Wesley, for example. There are books there on Java regarding Business Logic, Intelligent Agents, Design Patterns, Full E-Commerce Solutions. In other words, many of books on the subjects that grab the attention of CIOs and CEOs of major corporations.
In my opinion, KM, you need to do more than tell us about how this is done. You need to write a concrete text showing HOW it is done and WHY Perl is best-suited for the job. For, if we had to do something of this scale and robustness, most of us we would be lost.
In reply to Perl Behind the Scenes in Industry
by princepawn
in thread Can perl be anything like Java?
by pos
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |