docs/master
changeset 63:abbaca05ee8e
More text.
author | markus schnalke <meillo@marmaro.de> |
---|---|
date | Fri, 01 Jun 2012 22:32:27 +0200 |
parents | 24aabbfe5794 |
children | a0b678a9b583 |
files | ch03.roff |
diffstat | 1 files changed, 28 insertions(+), 3 deletions(-) [+] |
line diff
1.1 --- a/ch03.roff Fri Jun 01 17:15:38 2012 +0200 1.2 +++ b/ch03.roff Fri Jun 01 22:32:27 2012 +0200 1.3 @@ -205,8 +205,6 @@ 1.4 It's main use was for accessing Bulletin Boards, which have seized to 1.5 be popular. 1.6 .P 1.7 -XXX discuss 1.8 -.P 1.9 Removing 1.10 .Pn msh , 1.11 together with the truly obsolete code relicts 1.12 @@ -214,7 +212,33 @@ 1.13 and 1.14 .Pn wmh , 1.15 saved more than 7\|000 lines of C code \(en 1.16 -that's about 15\|% less code in the project. 1.17 +about 15\|% of the project's source code amount. 1.18 +Having the same functionality in less code (with equal readability, 1.19 +of course) is an advantage. 1.20 +Less code means less bugs and less maintenance work. 1.21 +If 1.22 +.Pn rcvtty 1.23 +and 1.24 +.Pn msgchk 1.25 +are rarely used and can be implemented in different ways, 1.26 +then why should one keep them? 1.27 +.Pn viamail 's 1.28 +use case is now partly obsolete and partly covered by 1.29 +.Pn forw , 1.30 +hence there's no reason to still have 1.31 +.Pn viamail 1.32 +around. 1.33 +.Pn conflict 1.34 +is not related with the mail client, and 1.35 +.Pn msh 1.36 +conflicts with the basic concept of MH. 1.37 +Both tools could still be useful, but not as part of mmh. 1.38 +.P 1.39 +It is a design goal of mmh to remove those parts that are rarely used. 1.40 +The project shall become more stream-lined. 1.41 +Rarely used and loosely related tools distract from the lean appearance. 1.42 +They require maintenance cost without adding to the core task. 1.43 +Therefore they were removed. 1.44 1.45 1.46 .H2 "Merge of \f(CWshow\fP and \f(CWmhshow\fP 1.47 @@ -262,6 +286,7 @@ 1.48 .H2 "Removal of Configure Options 1.49 .P 1.50 1.51 + 1.52 .H2 "Removal of switches 1.53 .P 1.54