I didn't see any explicit mention of this idea, but it's obvious in the other replies...
Why not start your own site which adds the criteria for Development Time, possibly broken down into Coding Time and Debugging Time? This should be weighted something like 10% or 1% of the CPU weighting (insert arguments for and against here).
And the various points about using native idioms to solve the same problem lead me to think that a Native Idiom score would be telling as well. Sure, by forcing all entries to avoid native idiom advantages, it shows what the performance of a generic, doesn't-fit-into-a-native-idiom algorithm would do. But it also avoids showcasing what programming areas each language excels at (performance wise). Add in the native idiom measure, and development time becomes apparent and interesting too.
Quantum Mechanics: The dreams stuff is made of
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||