From: "Octavian Rasnita" <[EMAIL PROTECTED]> > Well, this is a limited approach, generated exactly by the fact that some > programmers don't really care about all those who read, but care the most > about their own preferences.
We can't care about ALL those who read it. The best we can do is to care about MOST. I know it's inconvenient if you are not part of the majority, but there is little we can do. > I am blind and the visual clues don't mean anything, but make the things > harder to understand. > > If I need to read a thread of many email messages, which are usually > received in a separate folder for each mailing list, and where the messages > can be grouped by threads, I *already* know very well what that thread is > all about, and I don't need to re-read or skip tens of lines just in order > to read 2 or 3 new lines. > > So top-posting is recommended for this reason. That's nice and dandy if you do read the thread in one go. If you read the original message, then half a day later three separate responses, next day a response to the third response and another response to the original post and ... and of course in the meantime you read tens of unrelated messages and have your own things to take care of. In that case you do need that bit of a history, because more likely than not, you barely remember you read something that might have been related a day or two ago. So you'd have to scroll down to find out what is the author of this particular email responding to. Jenda ===== [EMAIL PROTECTED] === http://Jenda.Krynicky.cz ===== When it comes to wine, women and song, wizards are allowed to get drunk and croon as much as they like. -- Terry Pratchett in Sourcery -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] http://learn.perl.org/
