>
> > Aside from the fact that using a system Perl for deployment is a bad
>
> Could someone please explain that statement?
>
For more reasons than i can count...
a) System Perl is usually very very old and not maintained by the
community anymore, so you miss out on many important bug fixes
(http://perldoc.perl.org/perlpolicy.html#MAINTENANCE-AND-SUPPORT)
b) System Perl is always broken in some way or another, RHEL for
example removes very very important core modules like Scalar::Util.
c) Most distributions compile their Perl with options like ithreads,
which make your applications a lot slower than they have to be.
d) You can't update modules from CPAN, because of conflicts with
packages installed by your distribution. (missing out on bug fixes again)
e) Old old old modules in the package system... Debian stable for
example seems to still ship IO::Socket::SSL 1.76, which uses bad cipher
lists and doesn't support perfect forward secrecy. (oh, and Mojolicious
2.98... hahahahahaha... *sob*)
Personally, at this point i pretty much avoid trying to help folks that are
obviously using a system Perl, because it's just too much trouble. (if you
know how to use the tools necessary to make it work, such as local::lib,
you'd most likely not need my help in the first place)
--
sebastian
--
You received this message because you are subscribed to the Google Groups
"Mojolicious" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/mojolicious.
For more options, visit https://groups.google.com/d/optout.
