I don't write programs for me to understand, I write them for others to understand so I use the underscores to make it very readable. However I get your point about it, I liked the space bar handling the job.
That content confounds me. It sounds as if camel case would be OK if you were wilting the comments for yourself, but others need underscores, but I can't imagine that's what you're saying.
I think he is saying that to the "untrained eye", underscoring is (slightly) easier to read than CamelCase.
Myself, I don't mid CamelCase, but where it gets me into trouble is if I start using acronyms in the name already to save space, all of a sudden it reads ABCCamelCaseBit1, and then for readability it needs to become ABC_CamelCaseBit1, and that is 17 characters. Also, I end up using characters to denote if something is a Timer or a Stage, etc to differentiate it from the pushbutton or output, etc.
In short, I'm patiently waiting for the code to allow longer nicknames. But I will say I'd much rather have features such as the new Modbus Scanner. And the continual improvements/bug fixes that are openly acknowledged, fixed, and time-lined. Not too many software/tech companies are that open about their bugs.