I don't mean this in any bad way, I agree with that statement only if the Perl software development team doesn't know what the heck they are doing. I wouldn't even call them good Perl programmers then. Yes Perl, if you don't set up anything, gives you full power and freedom along with all of the negative consequences. Java does not and is highly structured and constrained and there usually is only one way (or a couple) to do it which in general is good for big enterprise projects.
I will repeat here what any good Perl programmer should already know and be using: In 2005 Perl guru Damian Conway wrote the long awaited (needed) book called Perl Best Practices (http://oreilly.com/catalog/9780596001735) thus establishing the standard doctrine on how to write good maintainable Perl code. But by itself it wouldn't have been enough as how would developers easily apply all the rules? So later came the CPAN module Perl::Critic and the entire Perl::Critic::* ecosystem, a full featured framework for creating and applying coding standards to Perl source code. Both the Eclipse IDE (with EPIC) and the Padre Perl IDE, the two most used IDEs (I'm excluding text editors such as emacs, etc), have full plugins utilizing the Perl::Critic modules so that you can easily develop enterprise maintainable Perl code. With the arrival of Moose, a really powerful postmodern object system for Perl, . One can now write consistent maintainable enterprise-class OO based code and where design patterns like you mentioned can be properly implemented. In fact Moose (and Perl 6) as OO systems have many advantages over Java's, one being that they have the concept of roles ( http://www.modernperlbooks.com/mt/2009/05/perl-roles-versus-interfaces-and-abcs.html ) Modern Perl: http://www.modernperlbooks.com/ Enlightened Perl: http://www.enlightenedperl.org/ In summary, if you are a Perl programmer and are up-to-date on what has been happening the past couple years then you know that all these myths about the language are flat wrong. -L On Tue, Mar 23, 2010 at 2:30 PM, Joachim Baran < [email protected]> wrote: > On 23 March 2010 12:42, Leandro Hermida <[email protected]> wrote: > > [..] In my opinion the is no reason to change to Java other than > > just because and this would be a shame. > Perhaps Java is more suitable for larger projects from a software > engineering point-of-view. There has been quite a lot of work being > done on design patterns in Java -- as opposed to Perl's TIMTOWTDI. > > BW, > Joachim > > -- > B.1079 Michael Smith Building > Faculty of Life Sciences > The University of Manchester > Oxford Road > Manchester > M13 9PT > United Kingdom >
