comment on

To repeat: "The only possibility of achieving really impressive increases in productivity is using other people's libraries." (Brucke Eckel, Thinking in C++, Prentice Hall, 1995).

IMHO, there is no way you (as a single person) can be sure what happens on your system today. The average computer system and its software components are much too complicated for this. In the time you need to understand the whole system, it will have changed away under your feet. You may be able to understand parts, but even this can be challenging if you work under time pressure.

Perl is a language for getting your job done.

If you want safe hardware, build your own.
If you want real OS security, go for OpenBSD.
If you want signed, vendor-approved code, go for Java.
If you want to guard against every possible known evil, join the ranks of the latest paranoia cult.

But please, let Perl be Perl.

Hm, that got pathetic. Ah, who cares.

Christian Lemburg
Brainbench MVP for Perl
http://www.brainbench.com

In reply to Re: A Fit on NIH by clemburg
in thread A Fit on NIH by footpad

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.


There's more than one way to do things
	PerlMonks