Re:Flakes – Proposed mechanism to package Nix expressions in...
by k__ on Saturday July 20, 2019 @02:00PM
(#20487283)
cough YAML cough
[ Parent
| on HN ]
Re:Flakes – Proposed mechanism to package Nix expressions in...
by marcosdumay on Saturday July 20, 2019 @03:39PM
(#20487846)
Oh, man, let's not go there. It's a silly place.
Re:Flakes – Proposed mechanism to package Nix expressions in...
by k__ on Saturday July 20, 2019 @09:39PM
(#20489431)
Somehow, right?
But why isn't there an ML with the good parts of YAML, but without the bad parts?
Re:Flakes – Proposed mechanism to package Nix expressions in...
by clhodapp on Saturday July 20, 2019 @10:28PM
(#20489620)
YAML (and TOML and even XML when it's being used in a tag-centric way instead of a text-centric way) are not markup languages. A markup language is one that allows you to assign meaningful annotations to regions within a chunk of textual content (e.g. "these three words are underlined", "this relates to footnote 3", etc.). YAML and TOML have both changed the meanings of their acronyms to try and distance themselves from their original misnamings as "markup languages".
Re:Flakes – Proposed mechanism to package Nix expressions in...
by marcosdumay on Sunday July 21, 2019 @01:14PM
(#20492366)
Anyway, the GP's question is a good one. Where are the configuration/serialization languages that import the only good parts of YAML?
AFAIK, one can not subset YAML and get something coherent. But one can start from scratch and use its concepts. I imagine the languages are not there just because nobody got the time to do them.
Re:Flakes – Proposed mechanism to package Nix expressions in...
by tannhaeuser on Sunday July 21, 2019 @03:15AM
(#20490320)
Yep. Maven (ugh) even has switched off entity expansion, a basic feature of XML/SGML, in favour of their own ad-hoc ${property} syntax.