|For performance tuning, nothing beats having your hands on a working system.
A tool/language that is more effective for development can get you to a working system faster, leaving you more time to study and profile. And often times that's enough to win out over a more CPU/RAM efficient language that takes longer to develop with.
In my career I've seen Smalltalk systems win out over C++ systems, either by outperforming them or by actually finishing ("We could never have build this with C++"); and I've seen a 100KLOC Perl application server win out over Java.
Getting there first can give you a big advantage.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||