[..] large programs often have a huge memory overhead because modules cannot be unloaded after use. In contrast, Unix shell pipelines enter memory, do their job, then exit.
I don't buy it. These issues are entirely orthogonal.
If your memory use bothers you, you can either fork, require Foo::Bar, exit or write a Perl script that uses the module in question and pipe through it - depending on which of either is more convenient in the case at hand.
You're making the same mistake as people who compare JSP with CGI scripts written in Perl and conclude that Java is better. What matters is the environment, not the language.
Makeshifts last the longest.
In reply to Re: Website Application Framework with Sybase, Apache & Perl: My Thoughts
by Aristotle
in thread Website Application Framework with Sybase, Apache & Perl: My Thoughts
by princepawn
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |