Perl, is impossible to manage on a large scale ( Read multiple development centers ) as every script is as unique as it's developer.
I can't accept or believe this. I see no reason why perl code should be any different from Java in this regard. I think it more comes down to mentality of the people involved. Project managers in perl have a lot of architecture related decisions to make before a large project can commence. In the Java world these decisions are made by the language so they need not be contemplated. Of course as a project manager/architect i would prefer the flexibility of perl, and the added responsibility of making wise decisions than the rigid framework of Java. But I think many project managers I know, (especially those from the "business side" of things) would prefer Java because then they dont have to make those decisions, nor be responsible for their outcome.
Part of the reason i say this is that a large perl project need not have more than one "script", being entirely composed of modules and objects that do the actual work.
First they ignore you, then they laugh at you, then they fight you, then you win.
-- Gandhi
In reply to Re: Re: ^7 OT: JavaJunkies (Javamonks sorta)
by demerphq
in thread OT: JavaJunkies (Javamonks sorta)
by coreolyn
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |