changeset 22:4c21f5b8d716

wrote about problems of MH (ch04)
author meillo@marmaro.de
date Tue, 02 Mar 2010 12:24:30 +0100
parents ca929b042039
children f0511a56416e
files unix-phil.ms
diffstat 1 files changed, 23 insertions(+), 4 deletions(-) [+]
line wrap: on
line diff
--- a/unix-phil.ms	Fri Feb 26 14:28:59 2010 +0100
+++ b/unix-phil.ms	Tue Mar 02 12:24:30 2010 +0100
@@ -1017,10 +1017,29 @@
 .NH 2
 Problems
 .LP
-modern emailing
-MIME
-encodings
-largest problem: different feeling
+\s-1MH\s0, for sure is not without problems.
+There are two main problems: one technical, the other about human behavior.
+.PP
+\s-1MH\s0 is old and email today is very different to email in the time
+when \s-1MH\s0 was designed.
+\s-1MH\s0 adopted to the changes pretty well, but it is limited.
+For example in development resources.
+\s-1MIME\s0 support and support for different character encodings
+is available, but only on a moderate level.
+More active developers could quickly improve there.
+It is also limited by design, which is the larger problem.
+\s-1IMAP\s0, for example, conflicts with \s-1MH\s0's design to a large extend.
+These design conflicts are not easily solvable.
+Possibly, they require a redesign.
+.PP
+The other kind of problem is human habits.
+When in this world almost all \s-1MUA\s0s are monolithic,
+it is very difficult to convince people to use a toolbox style \s-1MUA\s0
+like \s-1MH\s0.
+The habits are so strong, that even people who understood the concept
+and advantages of \s-1MH\s0 do not like to switch.
+Unfortunately, the frontends to \s-1MH\s0, which can provide familiar look'n'feel,
+are not very appealing in contrast to what monolithic \s-1MUA\s0s offer.
 
 .NH 2
 Summary \s-1MH\s0