1.  What? (anyway use cpanminus these days).
2.  Again what?
3.  Nope, there are a variety of tools available.  Try `cpanm Perl::PrereqScanner::App` followed by `scan-perl-prereqs .`
4.  Yeah you can skip test runs `cpanm --notest` , you really want to?  The subsequent complaint, you&#x27;re clearly having an experience I don&#x27;t have.  
5.  Again see cpanm
6.  Can&#x27;t comment on this one.
7.  Umm, that&#x27;s a code smell.  From cpan that outcome is rare.
8.  You use regexes when you need certain kind of things done fast.  Don&#x27;t forget the `&#x2F;x` flag to ensure it&#x27;s documented if a non-trivial regex.
9.  Actually I spend most of my time in the perl debugger.  Older perl codebases do suffer from the magic payload pattern quite a lot.  Modern perl, less so.
10. Yeah I agree, one should probably have to explicitly turn off warnings and strict, but whatever.<p>Anyway I agree, perl has made huge progress since the 1990s.  I also agree there&#x27;s a problem with discoverability in some parts of the cpan ecosystem.  Be sure to read the Modern Perl book next time you need to do some perl work.  You ought to be pleasantly surprised.  Personally with the Moo(se)? family of modules, I enjoy having a multiparadigm language with reasonable optional runtime typing to keep me sane.  My biggest complaint is the reference counted garbage collection.