Working in spring, which accepts I don't know how many formats from ENV_VARS to yaml, this very much resonates with me, because as a general rule, if one can use a certain option, someone will do it.
Also the reason why I try to avoid Gradle when possible:
The possibilities are endless. At one place I think I found 21 wildly different Gradle configs out of 24 that I checked.
(For anyone that wonders, it was combinations of:
- placeholders vs straightforward depency (this is a thing in maven too)
- for loops doing things based on lists or maps instead of just calmly declaring them one after another, maybe to save some characters
- helper functions so you could declare dependencies like azure(<something>(<version>))
- order of declarations
- Kotlin vs Groovy syntax
I have probably forgotten a couple more but this is thankfully already a few years ago.)
Also the reason why I try to avoid Gradle when possible:
The possibilities are endless. At one place I think I found 21 wildly different Gradle configs out of 24 that I checked.
(For anyone that wonders, it was combinations of:
- placeholders vs straightforward depency (this is a thing in maven too)
- for loops doing things based on lists or maps instead of just calmly declaring them one after another, maybe to save some characters
- helper functions so you could declare dependencies like azure(<something>(<version>))
- order of declarations
- Kotlin vs Groovy syntax
I have probably forgotten a couple more but this is thankfully already a few years ago.)