I bet you've not been exposed to many corporate email chains. Top-posting makes a lot of sense there. I often get copied on an email chains from which only the last part affects me. For example it will be a long discussion about some task and then I'll get copied because I'm the person who does X and need to help out. Bottom posting wouldn't work here for a number of reasons:
- I don't care about the project and its planning 20 emails ago - but I still may need some information from those emails. What I need is the task (at the very top) and context if required (at the bottom).
- If anyone tried to edit the history by removing unnecessary parts, they'd most likely remove the parts not important to them, but later on same questions would get repeated as soon as new people join the conversation.
- Leaving all needed parts and bottom posting / replying inline would result in 20+ levels of nesting and each inline section would become its own thread. This is just not possible to manage without some public archive with thread support.
Both styles have sense in different environments. I bottom-post to public mailing lists, because it makes more sense there. I top-post to other people at work where exchange==email, because it makes more sense there.
I used to bring up the same argument and the same quote about why top-posting is bad - but I guess I was wrong - I just didn't see the issue from the other side at that point. This makes me think that people top-posting in html on public mailing lists simply don't understand the other side either, but may adjust with time. As long as we don't assume either side is narcissistic and allow the possibility that we're not experienced in every possible scenario of Internet communication, we may just get along... Just try to adjust to the audience and environment sometimes. This may mean top-posting to some office; as well as fighting with your POS outlook to allow you to bottom-post to a mailing list in plaintext without any attachments.