Beefy Boxes and Bandwidth Generously Provided by pair Networks
go ahead... be a heretic
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Nothing really new to add - just confirming the opinions already express. I'm turning into a PHB, having done Perl development for the last few years, and now being in charge of the new wave of Java development at my company. I am involved in both sides of the argument and can see both the advantages and disadvantages of each. To me it has always boiled down to "the right tool for the right job" and Perl has been a pretty good tool. Unfortunately, most management decisions aren't based on such simple logic. We will keep using Perl for most of the supporting systems, monitoring tools and other related tasks. Our main production code will be Java for the reasons mentioned above - "Java is standard", and "there are many more, easily replacable, Java programmers than there are Perl programmers". What I am finding, from experience, is that 1) It takes a lot more hardware to to run an equivalent site under Java than it does under Perl, 2) Java programmers cost more than Perl programmers, 3) Not everyone that claims to be a Java programmer, is really qualified for the job, 4) everything seems to take longer to develop using Java, and 5) Good programmers are hard to find. A disturbing trend, but that is the direction things seem to be moving.

In reply to Re: Perl falls victim to shifting trends by Anonymous Monk
in thread Perl falls victim to shifting trends by vladb

Title:
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 How to display code and escape characters are good places to start.
Log In?
Username:
Password:

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

How do I use this?Last hourOther CB clients
Other Users?
Others avoiding work at the Monastery: (5)
As of 2024-04-23 12:50 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found