Doing most of my work in java, with one ongoing project written in perl (based on slahcode), I have to say I'm biased towards recommending perl for such a task: It is, to quote dragonchild once more, already 90% written in perl.
On the other hand: I recommend this, because to dive into the depths of slashcode taught me something about perl and how to programm it: but that took a fair amount of time (we released the first version with 4 weeks delay, some of that attributed to myself learning to love perl the hard way).
If you know how to code in java and how to use this internal framework, and this framework is actually suited for such a project, java may very well be your premiere choice ragarding your company and assuming you want to keep your job there.
One point in favour of perl is maintance time; maintaining a java application server (most of the time with apache on top) costs far more time than apache+mod_perl; and bug-fix / new-version cycles will take much less time.
regards,
tomte
Hlade's Law:
If you have a difficult task, give it to a lazy person --
they will find an easier way to do it.
In reply to Re: Choice of development language:Perl or Java
by Tomte
in thread Choice of development language:Perl or Java
by chimni
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |