+<item id="calling-the-shell-too-much" h="Calling Shell Commands Too Much">
+Some people are tempted to use shell commands for performing
+various tasks using <tt>`…`</tt>, <tt>qx/…/</tt>, <tt>system()</tt>,
+piped-open, etc. However, usually Perl has built-in routines or alternatively
+CPAN modules, which are more portable, and often would be faster than
+calling the shell for help, and they should be used instead.
+As an extreme example, the site <i>The Daily WTF</i>
+had <a href="http://thedailywtf.com/Articles/The_UNIX_Philosophy.aspx">a
+feature</a> which featured the following code to determine the file size
+my $filesize = `wc -c $file | cut -c0-8 | sed 's/ //g'`;
+Reportedly, replacing this line with <tt>my $filesize = -s $file</tt> (which
+as noted earlier should have been called <tt>$filename</tt> instead), resulted
+in the program being 75 minutes faster on average (!).
+Normally, if you find yourself using UNIX text processing commands such as
+<tt>sed</tt>, <tt>awk</tt>, <tt>grep</tt>, and <tt>cut</tt>, you should
+implement it in pure-Perl code.