It didn’t move anything. It simply showed the storage as it was stored in the container. The other sorts back then did nothing but change the display order but didn’t change anything in the storage itself. The sorts now change the order in the storage, and resort everytime you add something while active.
There is when you realize there is server performance and database size to worry about. If you save the position of every item under a custom sort, you double the size in memory of every storage container on the server.
One or two containers is negligible. Several thousand containers is another story. Again I’m not against this, but it is something that has to be taken into account. And something you want to test before applying it in a live patch affecting 6+ year old 12-20GB databases.