ron
dhall-lang
Our great sponsors
ron | dhall-lang | |
---|---|---|
24 | 113 | |
3,073 | 4,124 | |
2.1% | 1.3% | |
7.9 | 6.0 | |
11 days ago | 27 days ago | |
Rust | Dhall | |
Apache License 2.0 | BSD 3-clause "New" or "Revised" License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ron
-
XML is better than YAML
Whenever this kind of arguments come up, I am sad that RON (https://github.com/ron-rs/ron) is not better known. To me it feels like a cleaner and better JSON.
In any case, my little experience with it had made me hate YAML. Generally speaking, I have come to dislike any language with significant whitespace other than Haskell.
-
What config format do you prefer?
Part of the reason why I migrated away from RON in system76-scheduler is because I needed to rely on the 253-untagged-enums branch from https://github.com/MomoLangenstein/ron. Which still isn't resolved today: https://github.com/ron-rs/ron/pull/451.
Sounds like RON - Rusty Object Notation
-
Ron: Rusty Object Notation
Serde is strongly, strictly typed: you have to specify what type you want to decode to. It’s nothing like Python’s Pickle protocol.
See, for example, https://github.com/ron-rs/ron/blob/484fcab0686dfd18c7e29b6c1..., where it (in a type-inferency way) says “parse as Config”.
- JSON vs. XML with Douglas Crockford
- They're rebuilding the Death Star of complexity
-
Show /r/rust: deser, an experimental serialization system for Rust
Cool project! I ran into some limitations of serde a while ago while trying to add some new features to ron: https://github.com/ron-rs/ron/pull/328. Not sure if that's the kind of issue you are planning to address, but either way it's a concrete example of a use case where serde is currently not a perfect fit.
-
YAML: It's Time to Move On
You might like RON[1]. It's far from perfect (and far from complete), but seems nice so far.
-
The KDL Document Language
While there's JSON5[1] now, it just has not the same level of native (ecosystem) support as JSON has.
[0]: https://github.com/ron-rs/ron
[1]: https://json5.org/
dhall-lang
-
Apple releases Pkl – onfiguration as code language
Fail to see how this is any different than Dhall (https://dhall-lang.org/) other than it produces plists too.
Well, Dhall provides something between JSON and a Turing complete language that can make a lot of configuration much quicker to write, if you can hack the functional syntax.
-
Pkl, a Programming Language for Configuration
Kubernetes config is a decent example. I had ChatGPT generate a representative silly example -- the content doesn't matter so much as the structure:
https://gist.github.com/cstrahan/528b00cd5c3a22e3d8f057bb1a7...
Now consider 100s (if not 1000s) of such files.
I haven't given Pkl an in depth look yet, but I can say that the Industry Standard™ of "simple YAML" + string substitution (with delicate, error prone indentation -- since YAML is indentation sensitive) is easily beat by any of:
- https://nixos.org/manual/nix/stable/language/index.html
- (insert many more here, probably including Pkl)
-
Why the fuck are we templating YAML? (2019)
Indeed why? However the conclusion I have is not to use JSON but to use a type safe configuration language that can express my intent much better making illegal states impossible. One example of such lang is Dhall.
Throwing in a plug for https://dhall-lang.org/
> Dhall is a programmable configuration language that you can think of as: JSON + functions + types + imports
-
Is Htmx Just Another JavaScript Framework?
There are underpowered languages / tools, that can only solve a problem for which they are intended poorly. But not all limited tools are like that.
Say, eBPF is prominently not Turing-complete, which allows to guarantee that a eBPF program terminates, and even how soon. Still eBPF is hugely useful in its area.
Or, say, regular expressions are limited to regular languages; in particular, they famously [1] cannot process recursive structures, like trees. Still tools like grep / ag / rg are mightily useful.
Yes, I agree that YAML is underpowered for proper k8s configuration! But it's also too powerful for its own good in other aspects [2]. I wish Google used Dhall [3] or their own purely functional config language (FCL? I already forgot the name) instead of YAML; sadly, they did not.
[1]: https://stackoverflow.com/a/1732454/223424
[2]: https://ruudvanasseldonk.com/2023/01/11/the-yaml-document-fr...
-
10 Ways for Kubernetes Declarative Configuration Management
Dhall: Dhall is a programmable configuration language that combines features like JSON, functions, types, and import capabilities. Its style leans towards functional programming, so if you're familiar with functional-style languages such as Haskell, you might find Dhall to be quite intuitive.
-
Berry is a ultra-lightweight dynamically typed embedded scripting language
I've been thinking along these lines but more 'strongly validated' than statically typed in the sense that you'd be better off being able to load the entire config and then produce a list of problems (and should be able to offer good editor support if done correctly).
Though https://dhall-lang.org/ demonstrates that you can statically type quite a lot of configuration to great advantage, which appears to be programmatically embeddable in multiple languages per https://docs.dhall-lang.org/howtos/How-to-integrate-Dhall.ht...
-
What Is Wrong with TOML?
I agree, I quite like https://dhall-lang.org/ for that reason. It strikes a good balance between features and being a config language.
What are some alternatives?
cue - CUE has moved to https://github.com/cue-lang/cue
jsonnet - Jsonnet - The data templating language
toml.io - Source Code for toml.io
cue - The home of the CUE language! Validate and define text-based and dynamic configuration
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
jsonlogic - Go Lang implementation of JsonLogic
json5 - JSON5 — JSON for Humans
nix-gui - Use NixOS Without Coding
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
kdl - the kdl document language specifications
zig - General-purpose programming language and toolchain for maintaining robust, optimal, and reusable software.
yaml-reference-parser