comment on

It's much faster to write an application in Perl than in C or Java. Who can do anything useful in a comand one-liner in C or Java? Who can write a simple web site robot in 100 lines of C or Java?

Once the prototype is function, and benchmarking shows a deficiency, I consider that an approrpriate time to re-implement a component in C ... a native module or a chunk of Inline::C. If you're going to re-implement Perl code for speed, it makes little sense to use Java for that.

On the other hand, Inline::Java might be useful for interfacing to other Java code, taking advantage of other people's code.

After all, "Use Existing Code" always gets more done, faster, than "Not Invented Here."

Perl for fast implementation, C for fast code, Java when suitable for external code.

--
TTTATCGGTCGTTATATAGATGTTTGCA

In reply to Re: Is Java really better than Perl??? by TomDLux
in thread Is Java really better than Perl??? by Roger

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.


Welcome to the Monastery
	PerlMonks