Post History

From a [comment](https://meta.codidact.com/comments/thread/10342#comment-25924) "You haven't explained why that's supposed to be bad." I agree that feature requests should motivate a bit why they are posted because that information is needed to judge the requests anyway.

In this case the advantage would probably be a little more convenience by being faster and no scrolling back to the beginning of the page (although that might also be possible with an anchored link when reloading). The inconvenience by a reload however isn't that big in most cases.

On the other hand, there would be additional logic required to differentiate between both modes (in-place and with additional reload) and duplicated effort in once sorting on the server side and another time on the client side. It would increase complexity and maintenance effort of the code base (especially the duplication of the sorting).

Taking both together this feature should not be implemented because very likely there are more than enough features that deliver a higher return with lower effort.

Sidenotes:

Still, when doing the page reload, an anchor should be used to avoid scrolling back to the beginning of the page.

A more general discussion about which features should/could be done in-place (unfolding/folding of comments for example) and which rather should not would be interesting.