Interesting -- there are good reasons to use Perl -- fast to prototype, works easily on many platforms, all those yummy modules on CPAN -- yet speed, while very good, is not Perl's best feature.
For speed you do have to go to C or assembler -- that's something I know from experience. So at that point the question becomes, How much do you do in Perl, and how much in C? Should you bother to do *any* of the project in Perl?
I haven't written a large project in C in quite some time -- about ten years -- but when I have time, I'd love to do it again. With enough planning, the right structure and a great development environment, it would be lots of fun.
Alex / talexb / Toronto
"Groklaw is the open-source mentality applied to legal research" ~ Linus Torvalds
-
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.
|