4 ms·
Long time ago i thought .properties was bad, as it has no structure. But later I realized repeating full path to every config param is really good for readabili
by deepsun 5mo ago
Long time ago i thought .properties was bad, as it has no structure. But later I realized repeating full path to every config param is really good for readability, and code reviews.
The only thing I wish it had is @import-s from a separate files, that way we could split local/checkedin configs. YAML doesn't have @imports as well (only rudimentary from the same file), I have only seen them at HOCON.
- iririririr 5mo agoYou may be on to something. Imagine Yaml only in the editor. but stored (and code reviews consequently) are .property style.
- deepsun 5mo agoIDE (like IntelliJ) can already do syntax coloring, autocompletion a even schema checking for known .properties. I don't see a reason in short names if I don't type them anyway, it's all autocompletion.
- iririririr 5mo agoide doesnt save you from having the yaml in the wrong level. tried to look at a cloudinit file? it's pure insanity.