4 ms·

“requiredDuringSchedulingIgnoredDuringExecution” .. wow, what an epic length for a configuration option!

deleted 5y ago
[deleted]
mike_d 5y ago
Let me introduce you to CNLabelContactRelationYoungerCousinMothersSiblingsDaughterOrFathersSistersDaughter https://developer.apple.com/documentation/contacts/cnlabelcontactrelationyoungercousinmotherssiblingsdaughterorfatherssistersdaughter https://developer.apple.com/documentation/contacts/cnlabelco...
- aetherspawn 5y ago
  I doubt the person who released this did it with a straight face.
ur-whale 5y ago
>“requiredDuringSchedulingIgnoredDuringExecution” .. wow, what an epic length for a configuration option Looks like Java culture is alive, well and spreading.
- tecleandor 5y ago
  Seems Kubernetes-y: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity https://kubernetes.io/docs/concepts/scheduling-eviction/assi...
  - ur-whale 5y ago
    >Seems Kubernetes-y: Two guesses as to where the folks who implemented Kubernetes hail from (as in: which programming language)
    - dragonwriter 5y ago
      > 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.
hiyer 5y ago
I guess you haven't worked with Hadoop. Here's an example of what configuration option names in it can look like: dfs.datanode.available-space-volume-choosing-policy.balanced-space-preference-fraction
- virgilp 5y ago
  Is length really a problem? I definitely prefer this over, eg. dfs.datanode.asvcp.bspf
  - kubanczyk 5y ago
    Naming things is hard. There are a lot of users of Transmission Control Protocol/Internet Protocol and users of American Standard Code for Information Interchange who disagree with you. It's more of a social endeavor than anything else.
    - virgilp 5y ago
      Nice. I 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.
deepsun 5y ago
And that's a good thing. k8s configurations are rarely written. It's better to make them as clear as possible, even if it makes them verbose and long-to-type. 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.

deleted 5y ago

[deleted]

Let me introduce you to CNLabelContactRelationYoungerCousinMothersSiblingsDaughterOrFathersSistersDaughter https://developer.apple.com/documentation/contacts/cnlabelcontactrelationyoungercousinmotherssiblingsdaughterorfatherssistersdaughter https://developer.apple.com/documentation/contacts/cnlabelco...

aetherspawn 5y ago
I doubt the person who released this did it with a straight face.

ur-whale 5y ago

>“requiredDuringSchedulingIgnoredDuringExecution” .. wow, what an epic length for a configuration option Looks like Java culture is alive, well and spreading.

tecleandor 5y ago
Seems Kubernetes-y: https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#node-affinity https://kubernetes.io/docs/concepts/scheduling-eviction/assi...
- ur-whale 5y ago
  >Seems Kubernetes-y: Two guesses as to where the folks who implemented Kubernetes hail from (as in: which programming language)
  - dragonwriter 5y ago
    > 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.

hiyer 5y ago

I guess you haven't worked with Hadoop. Here's an example of what configuration option names in it can look like: dfs.datanode.available-space-volume-choosing-policy.balanced-space-preference-fraction

virgilp 5y ago
Is length really a problem? I definitely prefer this over, eg. dfs.datanode.asvcp.bspf
- kubanczyk 5y ago
  Naming things is hard. There are a lot of users of Transmission Control Protocol/Internet Protocol and users of American Standard Code for Information Interchange who disagree with you. It's more of a social endeavor than anything else.
  - virgilp 5y ago
    Nice. I 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.

deepsun 5y ago

And that's a good thing. k8s configurations are rarely written. It's better to make them as clear as possible, even if it makes them verbose and long-to-type. 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.