comment on

With scripts, you can see what you are getting.

You haven't been looking at the obfu section of this site much lately, have you? :)

Seriously, given that perl offers run-time eval and a very powerful regex language with side-effects, you have to have just about the same amount of trust in the person that hands you 1000 lines of perl code as you need in 100k of executable.

Either one could do totally unexpected things without you being able to tell by inspection.

I'm not saying "scripting languages bad"; what I am saying is that the source being in front of you doesn't mean much.

And as processor speeds increase, the delay caused by script compiling is becoming negligible.

There are many areas where that's just not true. A lot of programming problems have time constraints, where if the answer is late it's just about worthless. And those constraints often get tighter just as fast as processor speeds increase.

Mike

In reply to Re: Re: On Scripting versus Compiled solutions by RMGir
in thread On Scripting versus Compiled solutions by clintp

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.


Perl: the Markov chain saw
	PerlMonks