Well, I did not read the whole final report yet, I skipped some sections, but I would not exactly say it Perl is apperently the best. It was the best in some aspects and not so good in others. I think it did not do as well as expected, while the other two did better than expected (all expectations mine of course). I believe there's a lot to learn from and improve in the frameworks for the next round (and for actual projects). As it is, I'd say we failed :-( Even though it seems, that if the project was for 40 instead of 30 hours and/or included some "OK, guys, this and this and this should be changed" anounced sometime later in the project, the Perl teams would do much better.
I guess we'll see a lot of "this comparison is not fair because ..." and "you should measure this and that" and "this is completly irrelevant, but ..." posts all over the net for some time now :-)
-
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.
|
