Sorry to bring back this topic... But let me disagree with what was said here, and let me explain why.
Currently, we're having performance issues with one application, and that is mainly because of the huge ids that lead to huge HTML.
While rendering a page this is "not that important", that's not the same when we talk about Ajax Refresh!
We have a complex table records, and when we do filter, we have an Ajax Refresh to refresh the table, this will be called through one XHR call by the platform, as shown below:

This response contains all the HTML that was changed due to the filtering, and is "returned" from the Ajax Refresh, and as I said our table is a bit complex, making this response size around 1.8mb (and trust me, it was already highly refactored to have fewer nodes as possible).
While the server might compress the payload, we still have to process this 1.8mb!
The platform first injects this 1.8mb in the HTML document, and after that the OsJSONUpdate still needs to process 1.8mb of data, and part of that process will be writing back the html to the page.
That being said, if we had smaller Ids, we would have way less than 1.8mb of HTML to process!
That are my 2 cents on this matter :)