I don't disagree that top posting is often the result of laziness, but I think the logical thread of the articles starts to break down at this point: > But whe

I don't disagree that top posting is often the result of laziness, but I think the logical thread of the articles starts to break down at this point: > But when the thread is long, and when your reply is to a point deeper inside, suddenly the receiver has to do a lot of work. You, the sender, have saved yourself time, but the receiver has to do more work than you have saved. Potentially a lot more work. The problem is that readers are also lazy, and increasingly people don't have time to follow long threads at all. With inline responses, it's far too easy for threads to branch off in a million directions. Once that happens you'll often lose the forest for the trees. It's reasonable for usenet-style internet discussions where participation is voluntary and asynchronous by definition, but in work collaboration it's a strong anti-pattern. In a situation where there is a goal and desired outcome, top-posting is a reasonable way to keep a thread linear and outcome-focused. It can still break down for complex or controversial issues, but in that case email is the wrong medium, instead jump on a call or write a proposal.