comparison unix-phil.ms @ 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
comparison
equal deleted inserted replaced
21:ca929b042039 22:4c21f5b8d716
1015 .] 1015 .]
1016 1016
1017 .NH 2 1017 .NH 2
1018 Problems 1018 Problems
1019 .LP 1019 .LP
1020 modern emailing 1020 \s-1MH\s0, for sure is not without problems.
1021 MIME 1021 There are two main problems: one technical, the other about human behavior.
1022 encodings 1022 .PP
1023 largest problem: different feeling 1023 \s-1MH\s0 is old and email today is very different to email in the time
1024 when \s-1MH\s0 was designed.
1025 \s-1MH\s0 adopted to the changes pretty well, but it is limited.
1026 For example in development resources.
1027 \s-1MIME\s0 support and support for different character encodings
1028 is available, but only on a moderate level.
1029 More active developers could quickly improve there.
1030 It is also limited by design, which is the larger problem.
1031 \s-1IMAP\s0, for example, conflicts with \s-1MH\s0's design to a large extend.
1032 These design conflicts are not easily solvable.
1033 Possibly, they require a redesign.
1034 .PP
1035 The other kind of problem is human habits.
1036 When in this world almost all \s-1MUA\s0s are monolithic,
1037 it is very difficult to convince people to use a toolbox style \s-1MUA\s0
1038 like \s-1MH\s0.
1039 The habits are so strong, that even people who understood the concept
1040 and advantages of \s-1MH\s0 do not like to switch.
1041 Unfortunately, the frontends to \s-1MH\s0, which can provide familiar look'n'feel,
1042 are not very appealing in contrast to what monolithic \s-1MUA\s0s offer.
1024 1043
1025 .NH 2 1044 .NH 2
1026 Summary \s-1MH\s0 1045 Summary \s-1MH\s0
1027 .LP 1046 .LP
1028 flexibility, no redundancy, use the shell 1047 flexibility, no redundancy, use the shell