Slash Boxes
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.
  • Unless you're certain that the VP meant "optimal" in terms of performance, I'd look at the question again. Answering that you can handle the transaction load might not address his concerns. He could be worried about several other things, such as "If you write that in Perl, will we be able to maintain and support it?" or "If you leave, will we be able to find someone else to pick it up?" or "Is Perl really a serious language?"
    • what I was trying to do in my own (brief) analysis is defend exactly the three points you bring up: yes, the software is supportable (well documented); yes, others will be able to maintain it (with a test suite, at least they can't break anything that currently works); yes it's a serious language (it can take advantage of OO like everyone else).

      I actually didn't expect that he meant performance :)
  • What are your choices? Saying how much longer in time and code would it be in Java, .NET, or PHP is a good response.


    • actually, I suspect that he's leaning either toward java (the company standard) or something more abstract, like "XML" - both of which fit the nature of the project. What he will likely be shocked to find is that I've been advocating (and capable of supporting) the use of direct SOAP calls to my API for a while (as opposed to the daemon approach it uses now - SOAP::Lite++). I keep hoping somebody will take me up on it so I can giggle as the Java people try and keep up :)