I never said that big-endian was "best". From the point of view of a machine it is arbitrary indeed and it does not matter (it may have mattered in the past). But form the point of view of a human, big-endian feels more natural. Even that is just a convention, but a convention that we learned as little children and that we use every day, along with everybody around us. If I want to write down the square of 7 in decimal, I go for 49 (big-endian) instead of 94 (little-endian). I could interpret 94 as the square of 7, but that would require a constant effort and introduce a lot of mistakes as soon as I'm not paying attention and just reading casually.
This is precisely why, without even thinking about it, and before finding out that the arduino tends to be little-endian, I favoured a big-endian scheme for saving integers to EEPROM. And then there came the clash between my bespoke solution and the methods from the EEPROM library. I've said it many times already along this thread.