I appreciate the comments, some things to think about.
If you have planned tables and data properly uniqueness should not be an issue and it looks like the performance consideration is unlikely to be a problem in most cases.
Being able to check the raw data easily with a standard global naming is, for me at least, a benefit of not using the hashed names.
However, knowing these reasons is very helpful in planning and identifying those edge cases.
Is there anything else I have missed that would make this more of an issue?
Without someone providing an accepted linter you won't get everyone to agree on case etc...
My own preferences do not all match the above but if we had a defined ruleset that was easily managed and enforceable in the IDE then fine with me.
However, I think we should all be able to agree that moving away from shortened commands and names benefits code maintenance and readability plus aligns better with other languages, especially if we use classes, braces, and other "modern" objectscript styles. Yes I know that I am showing my age, but note I avoided mentioning the "M" word 😂
This looks so much easier than when I had to do it and is very welcome.
At the time I moved it to a personal email so I didn't have to do it again changing companies.
This means it should actually be possible to keep it linked to wherever you are working.