As I see it (short version): 1. snake_case - best of the best. words are separated, easy to read even if the words are not in english or latin 2. ShrtCmlCase

As I see it (short version): 1. snake_case - best of the best. words are separated, easy to read even if the words are not in english or latin 2. ShrtCmlCase - worse than snake. Pros: quite short, does not take whole monitor width. Cons: requires additional thinking and some sort of in-team guidelines. Very opinionated. 3. JavaCamelCase - worse than ShrtCmlCase. Pros: you can put in and describe anything in a single name of a class\variable. Cons: you spend too much attention on reading rather than analysing the program. I can understand why Java uses long names though. Its oop and enterprise nature is to "blame". This kind of naming is unavoidable when you are building a giant monolith with hundreds or thousands of classes, all kind of inheritance nuances and trying to have all names actually mean and describe something.