What you're doing here is adding your own personal requirements and claiming that they are basic necessities. It's just not true.
Yeah, I understand this. But I wish to discuss this situation because I think 'worksforme' software is evil. If I'm only person on perlmonks who think this way - I just wish to know it, what's wrong with this?
Not everyone needs IPC that supports pipes and lists.
Yep. But no one needs IPC which may hands because of lack of timeout, may incorrectly handle signals in some environment (which developer can't prevent because it's environment where his software will be used), etc. Especially no one needs such IPC hidden inside CPAN modules, at least without bold WARNINGs about this in documentation.
Not everyone needs timers that handle someone changing the clock under them.
Can't agree with this. If software has timeout for some operation 15 seconds, but may sometimes (because of NTP daemon, which is part of environment configured by admin of your system without notifying you) finish timeout in 0.5 sec - it's a BUG in this software. Why you think having this bug in nearly all CPAN modules is goodness?
Adding those features is time-consuming and expensive.
Yep. Usually (using clock_gettime(CLOCK_MONOTONIC) isn't more time-consuming than using time() - it may be less portable, but that's another story, portability IS a feature, while reliability isn't a feature).
But if many monks here agree reliability & security is 'mush have' goals, then next we can discuss how to make these goals not so expensive and time-consuming.

In reply to Re^4: Reliable software OR Is CPAN the sacred cow by powerman
in thread Reliable software: SOLVED (was: Reliable software OR Is CPAN the sacred cow) by powerman

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.