Programming our ERP system we also use a reverse sort order for our logfiles. You get the latest replies / entries first - then you follow the history. Most of the time for the current posts the long log is not necessary, it doesnt matter what a customer has written 3 months ago. Therefore the latest 2-3 posts are sufficient. You read the answer first, if you need more details you scroll down and read the post before and the one before. As said, most of the times you do not need to go more back in history than 2-3 posts - the rest is irrelevant and can be accessed by scrolling in case you need it. Reversal allows you to scan the posts before for the relevant things as you have already open questions or details read in the current new post and know what to look for. Having a chronical order you might need to jump backwards as you got to know later what the current post refers to and might have skipped that already or forgotten. So you need to go back again. Reversal order way is faster in dealing with the posts as you have the current questions/details in mind (short memory) - same as in the forum. But I guess this is maybe more a "believer" thing.
Marcus Sternberg got a reaction from kmk in Sorting posts by reverse
