It doesn't. Nothing prevents you from adding/committing several days worth of work with a "changed stuff. fixed some other stuff" commit message.
If people have good reasons for not doing certain things, then fine, but when people are just averse to it because they're lazy, well, that irks me (when I have to deal with them.)
I didn't speak up about it because I was only a contractor at the time, but it made me wince to see a whole history list of his commits with like 20 "latest and greatest" and maybe three commits that actually said what he did.
But most places I've been to, people have been pretty good about explaining what they've committed, when version control was being used.
git log --pretty=oneline --abbrev-commit --graph --stat
Seeing the names of the changed files in each commit gives me a lot more of context than simply the commit description.
At my current job we have dev tasks associated with the changesets (if applicable), so that helps provide context also.
I would recommend learning git for anyone. Sure, it's a big hassle, because it forces you to rethink your habits. But in the end, learning it has done me nothing but good and using it enforces me to follow good practice at the same time.
Also, just the support of 'git stash' to throw away experiments that didn't work easily is worth it. Tagging versions for release, demos, whatever .. git can help there too.