Hi there, in reply to his questions... >not have a "father". What if >those people lose interest. >What if we have a problem >and those kids are not >interested in fixing it. We >cannot afford to invest in >something so risky. What about all those VB6 applications everybody got stuck with VB.NET? What about Sun fiering 10% of it's staff? Very relative argument, risk
>can >buy the same things for >Java. >Where can I buy support for >those libraries on CPAN ? >What about copyright issues >? I'll need to ask our lawyer >($200/hour) for every >library we download. You can buy, yes. And have your staff waiting in line for tech support. Jar's also have licenses. >Perl is >an old langugage, does it >have objects anyway ? The point being? >So you say it >might not fit? I want to >decide on our language of >choice NOW ! And yes, BTW >what you pay is what you >get. A bad implementation can allways happen, regardless of language. And if you're not 100% sure whatever the choice, Perl has this advantage over non-free competitors. Btw: what you pay is what you get? Have you heard of Vignette :)) >Hardware is >cheap, it is not relevant. >Does Perl have such a wide >choice of Application Servers >? Hardware is cheap? Good for you, my friend :) Perl and 9iAS don't go together. I can live with that, can't say it makes me sad :) >Perl >scripters can't even read >each others code. Well, most of the time it's Open Source, so yes we can ;) >Perl is an >interpreted scripting >languge. It is known to be >slow. Although not like some years ago, JVM's are still slow. C is faster. Well, there are great modules for caching at CPAN your lawyer should know of, like storable and mason. You can allways tune your applications very easilly and effectively in Perl >Installing >50 modules from CPAN is a >nightmare. Although I don't agree, it's done only once, although 50 is a big number. There's a CPAN module that helps you do the job. If you can't already do it through some package manager, of course >Does it run on mobile phones >and on PDAs ? Porting your J2EE applications to J2ME is not an easy task. Is this a requisite? >So what are the pros ? Listen, my advice to you is: think very carefully about your real needs and everything else will follow. There is a number of pretty decent languages, and Perl is one of them, and so is Java. First just find out what your real needs are before you decide. Otherwise you're just having a 'yet another vi vs. emacs' academic discussion. If you have the freedom of choice, choose wisely. Cya
