Not necessarily due to muscle memory and easy of access upon keyboard or mostly soft keyboard layout for punctuation access. But mostly muscle memory. Heck co

Not necessarily due to muscle memory and easy of access upon keyboard or mostly soft keyboard layout for punctuation access. But mostly muscle memory. Heck could even view having to add the extra layer of shortening a two words into one is a process born out to save ink in a time when ink and print space was more costly and perhaps a form of lazyness that is more accepted than just having the full words. Like most things, perspective plays a part in how you view such things and we are all aware that such oversights can trigger people as much as those triggered responses being triggers for others. Which is odd as the meaning of words is how to communicate and in the instance of shorting words, nothing is lost in translation. But then standards in words and layout, styles, when it comes to standards are more complex than any coding standards and we all know how legacy code works out when it comes to standards. Another way to view that is, imagine if COBOL had as many verbs as we do English words - yeah scary what legacy code would look like then and sorry if that becomes the source of any nightmares in old COBOL programmers with that analogy.