I've seen the research paper too.

Note that the comment you're linking to suggests leaving it up to developers for application code but sticking with camel case for code that's being consumed elsewhere. I wouldn't mind as much for a submission, but as an example I think it bears thinking about.

I don't care about 2 vs 4 spaces, or newlines at the end of the file because I've not observed those causing a problem on real projects. Every time snake case is used on a large project, though, I see additional overhead as people try to remember if the method they're typing is supposed to be camel or snake.

I used to be in the camp of "whatever" on this one, but I've just seen this cause enough pain that I would really prefer to educate developers in a less painful way by default.