I am much obliged to all monks here. Now I've answer which I looking for in my initial post!
My initial post was very incorrectly formulated, but that's because to formulate question correctly you need to know at least half of answer, which I did't know at that time.
My initial post (and most comments) was deliberately designed as rant, because I've feeling I need much more than usual 3-5 comments to find answer. I'm sorry about this, but it's worked! :)
Now, in hope this helps somebody in the future, I'll repeat my question (better formulated and without rant), with answer.
Q: Why not develop everything with maximum possible reliability and security? Isn't world become better if our OS will be designed like Inferno and all software will be as reliable and secure as DJB's?
A: Because there different goals in development:
- If you need to "have your work done", then "works for me" is right way.
This way your software will be as reliable and secure as spec require, no more and no less. If you wish to improve overall software quality in the world in this case, you must try to increase spec requirements to reliability and security (i.e. go talk with your boss/customer).
- If you need to get maximum possible reliability&security, like DJB do, then you need to have a lot of time, experience, and be able to change spec if it require something you can't develop as reliable&secure as you wish.
This is more like intellectual game.
Such sort of development doesn't even guaratee you'll "have your work done" at some point, a good example of this is unfinished DJB's Internet Mail 2000 project. Also it doesn't guarantee your software will be useful for somebody, because people may need features which you've removed from spec (and that's why we've so many custom patches for Qmail).
There also exists slightly more
abstract answer. If you experienced enough, then you able to develop software per ANY spec. If spec will require DJB-like quality - no prob. If spec will require low quality cheap software developed very quickly - no prob. This way we've no more
different goals, just
different specs. And it's always up to you, agree to THAT spec, or not, and look for different work instead.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.