As you say, it&#x27;s about conventions, but with a case-Sensitive system you are more likely going to HAVE TO enforce naming conventions, because there&#x27;s a distinction now. Otherwise you&#x27;d write &quot;MidiPort&quot;&#x2F;&quot;MIDIPort&quot;&#x2F;&quot;midiPort&quot; or what have you.<p>Keep in mind we wouldn&#x27;t need to care about enforcing case in a style guide, if case didn&#x27;t matter, because there are no distinctions, and you&#x27;d be more inclined to write it the natural way; no camelCase to overrule ambiguation in writing &quot;MIDI Port&quot; as midiPort, or MidiPort, MIDIport, etc.<p>Case-sensitivity only creates unnecessary dissonance, and leads to clever uses of that system, adding even more choice; and as we know from The Matrix, the problem is choice. ;)<p>So if we keep it closer to how we would normally read and write words, I think there would be less dissonance about that aspect of programming, or naming files for that matter.