1.1 --- a/thesis/tex/4-MasqmailsFuture.tex	Tue Dec 30 13:22:56 2008 +0100
     1.2 +++ b/thesis/tex/4-MasqmailsFuture.tex	Tue Dec 30 13:34:08 2008 +0100
     1.3 @@ -64,7 +64,7 @@
     1.4  
     1.5  
     1.6  \subsubsection*{Robustness}
     1.7 -Being robust means handling errors properly. Small errors may get tolerated, large errors may kill a process, to get restarted afterwards. Log messages should be written in every case. Robust software does not need a special environment, it creates the right environment itself. \person{Raymond}'s \name{Rule of Robustness} and his \name{Rule of Repair} are good descriptions.\cite[page~18--21]{raymond03}
     1.8 +Being robust means handling errors properly. Small errors may get tolerated, large errors may kill a process, to get restarted afterwards. Log messages should be written in every case. Robust software does not need a special environment, it creates the right environment itself. \person{Raymond}'s \name{Rule of Robustness} and his \name{Rule of Repair} are good descriptions.\cite[pages~18--21]{raymond03}
     1.9  
    1.10  
    1.11  \subsubsection*{Extendability}
    1.12 @@ -72,7 +72,7 @@
    1.13  %fixme: like old sendmail, but not too much like it
    1.14  
    1.15  \subsubsection*{Maintainability}
    1.16 -Maintaining software takes much time and effort. \person{Spinellis} measures ``40\% to 70\% of the effort that goes into a software system is expended after the system is written first time.''\cite[page~1]{spinellis03} This is maintaining work. Hence making software good to maintain is effort that will become invalueable afterwards.
    1.17 +Maintaining software takes much time and effort. \person{Spinellis} measures ``40\,\% to 70\,\% of the effort that goes into a software system is expended after the system is written first time.''\cite[page~1]{spinellis03} This is maintaining work. Hence making software good to maintain is effort that will become invalueable afterwards.
    1.18  
    1.19  
    1.20  \subsubsection*{Testability}
    1.21 @@ -80,7 +80,7 @@
    1.22  
    1.23  
    1.24  \subsubsection*{Performance}
    1.25 -Also called ``efficiency''. Software requiring few time and few resources is nice. But as performance improvements are in contrast to many other quality poperties (reliability, maintainability, usability, capability \cite[page~5]{kan03}), japardizing them to gain some more performance should not be done. \person{Kernighan} and \person{Pike} state clear: ``[T]he first principle of optimization is \emph{don't}.''\cite{kernighan99}
    1.26 +Also called ``efficiency''. Software requiring few time and few resources is nice. But as performance improvements are in contrast to many other quality poperties (reliability, maintainability, usability, capability \cite[page~5]{kan03}), japardizing them to gain some more performance should not be done. \person{Kernighan} and \person{Pike} state clear: ``[T]he first principle of optimization is \emph{don't}.''\cite[page~165]{kernighan99}
    1.27  
    1.28  The merge of communication hardware and the move of email services from providers to homes, demands smaller and more resource-friendly software. The amount of mail will be lower, even if much more mail will be sent. More important will be the energy consumption and heat emission. These topics increased in relevance during the past years and they are expected to become more central. \masqmail\ is not a program to be used on large servers, but to be used on small devices. Thus focusing on energy and heat, not on performance, is the direction to go.
    1.29