If you’ve seen any amount of Go and Java code (starting with, say, the standard libraries), you’d know these communities take very different approaches to variable names.
First off, OP is talking about a trend in the community to favor shorter and shorter names. He didn't say you need to code that way, but there is an increasing chance that the programmers you work with, or the libraries you depend on, will have adopted this convention.
Second, unless you are coding in a vacuum or starting a brand new project, you're usually expected to follow the conventions of an existing codebase. These were likely influenced by conventions in the community, which often are set by conventions in the standard library, which have much to do with the language.
If there was one true way to do it, everybody would adopt it (unless you consider some communities are just plain dumb).
> 2.1. Choose identifiers for clarity, not brevity
Cosmetic considerations like snake or camel case are irrelevant.
The advice above is standard good practice that is not dependent on the language used.