https://developer.apple.com/documentation/contacts/cnlabelco...
dfs.datanode.available-space-volume-choosing-policy.balanced-space-preference-fraction dfs.datanode.asvcp.bspfI think this gives a hint though - when something is very-frequently-used, people need a short name so that it doesn't stand in the way of the discussion; and due to frequency, the fact that it's an acronym doesn't matter: I bet there are more people know what ASCII is than there are people who know what the acronym stands for.
For configuration, though? asvcp.bspf is never going to be frequently used by anybody. That's generally the point of configuration, for the vast majority of cases, you touch it at most once. So I argue you want long names.
Same thing can be said about build scripts. Those who strive for terseness (hey sbt) become unreadable mess 1 year after writing, when you need to read them again.
Looks like Java culture is alive, well and spreading.
https://kubernetes.io/docs/concepts/scheduling-eviction/assi...
Two guesses as to where the folks who implemented Kubernetes hail from (as in: which programming language)
Go, obviously, though from their rationale article they “love” C/C++, Java, and Python, too.