Beefy Boxes and Bandwidth Generously Provided by pair Networks
Perl-Sensitive Sunglasses

comment on

( #3333=superdoc: print w/replies, xml ) Need Help??

I would play on:

  • licensing costs (WebSphere is expensive)
  • training costs (WebSphere with VisualAge for Java is a sure productivity killer - just been there)
  • rapid development and incremental approach (Perl) vs. framework/waterfall/customization approach (WebSphere)
  • interfaces to external systems - Perl is adaptable, WebSphere either provides adapters or you are lost
  • complexity - is something like WebSphere really needed
  • how big will the development team be - with Perl you can get something done with a few people (one to five), with WebSphere you will have to have many different specialists (three upwards) to get anything done
  • show the client a convincing solution for support, with respectable names on this
  • provide respectable references that use Perl for commercial applications, e.g., from the DBI references list

I think you will lose, though. I have tried to argue this exact case with several big clients, and lost all arguments (might be my fault, of course). Try to define a cut-off point to decide how much resources you will spend on trying to convince the client. Otherwise this might become an acquisition resources black hole. (Extremely sorry to say this, but it is my experience.)

Christian Lemburg
Brainbench MVP for Perl

In reply to Re: Client prefers java, but wants to hear a case for Perl by clemburg
in thread Client prefers java, but wants to hear a case for Perl by Ovid

Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":

  • Are you posting in the right place? Check out Where do I post X? to know for sure.
  • Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
    <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
  • Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
  • Want more info? How to link or or How to display code and escape characters are good places to start.
Log In?

What's my password?
Create A New User
Domain Nodelet?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others about the Monastery: (4)
As of 2022-08-12 02:12 GMT
Find Nodes?
    Voting Booth?

    No recent polls found