3 ms·
fully agree, especially with the second paragraph. even as a developer, i want a simple DSL that lets me declare things and not twist the data structures into c
by em-bee 3y ago
fully agree, especially with the second paragraph. even as a developer, i want a simple DSL that lets me declare things and not twist the data structures into code. and especially as a programmer, if code is needed for more complex structures, i want that to be done in a real programming language.
so i am favoring the two products approach, or maybe a language with a well designed syntax for data, where the relationship between the two is like that of JSON and javascript.
- chubot 3y agoFWIW the JSON/JavaScript design is roughly where we're going with Oils We have JSON support for literal data, pure data But you can also interleave code and data in what turns out to be a very Lisp-y fashion, which is useful for configuration https://www.oilshell.org/release/0.17.0/doc/hay.html https://www.oilshell.org/release/0.17.0/doc/hay.html Slogan: We're adding the missing declarative part to shell, called Hay (Hay Ain't YAML) That is, most YAML configs are just nested key-value pairs, where some values are shell snippets ... So I think it makes sense to add declarative data to shell instead!