&gt; 1) The perl cpan module doesn&#x27;t resolve dependencies<p>What? CPAN absolutely does.<p>&gt; 2) The cpan module has parsing errors when passing in a list of CPAN packages<p>Both from the commandline, and in CPAN itself can i install a list of modules as such:<p><pre><code>    cpan Data::Dumper Devel::Confess
    
    install Data::Dumper Devel::Confess
</code></pre>
&gt; 3) You have to manually grep your perl code to see what modules it depends on<p>Or you can use a CPAN module for that.<p>&gt; 4) Module installs take a long time since they can compile and unit test the code<p>Or you just install them like this, if you&#x27;re confident in your system:<p><pre><code>    install Data::Dumper Devel::Confess
</code></pre>
&gt; 5) Non-interactive installs of CPAN modules requires digging in the docs<p>Non-interactive installs should be using your operating system&#x27;s package manager, unless you have a special use-case, in which some doc digging is fine.<p>&gt; 6) CPAN modules aren&#x27;t used that heavily and can have bugs that would be caught in wider used modules.<p>You mean &quot;<i>Some</i> CPAN modules&quot;.<p>&gt; 7) Perl devs don&#x27;t think twice about shelling out to an external binary (that may or may not be installed)<p>Again, <i>some</i>.<p>&gt; 8) Even if regexs are not needed, inevitably the perl dev will use them since that&#x27;s the perl hammer<p>Eh, fair enough.<p>&gt; 9) You have to manually include the DataDumper package to debug data structs<p><pre><code>    Data::Dumper was first released with perl 5.005
</code></pre>
&gt; 10) You have to manually enable warnings and strict check, it&#x27;s not on by default.<p>Same in JS, and similar with other languages.<p>&gt; Anyhow, I think we&#x27;ve made a lot of progress since the 1990s. :)<p>Not really sure, the trolling culture seems to still be the same as back then.