apt-get all have sub-commands (is there a better name?), and they are all case-sensitive:
hg log # not hg Log git status # not git Status sudo apt-get install nano # not sudo apt-get Install nano
Obviously a lot of things in Unix need to be case-sensitive, because that's kind of how Unix is.
But in this case, there's no potential ambiguity. Those arguments can only be command names and can't be anything else (can they?).
git's error message suggests that this is the case:
> git Status git: 'Status' is not a git command. See 'git --help'. Did you mean this? status
Besides adding just a little more frustration for beginners and conforming to Unix culture, is there any reason to be case-sensitive?