lua-patterns
ron
Our great sponsors
| lua-patterns | ron | |
|---|---|---|
| 1 | 24 | |
| 27 | 3,096 | |
| - | 1.8% | |
| 0.0 | 7.9 | |
| over 1 year ago | 7 days ago | |
| Rust | Rust | |
| MIT License | Apache License 2.0 |
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.
lua-patterns
-
The Norway Problem
If you want automatic built-in string validation, one option that seems particularly interesting is to use a variant of Lua patterns, which are weaker and easier to understand than regular expressions, but still provide a significant degree of "sanity" for something like an email. The original version works on bytes and not runes, but you could simply write a parser that works on runes instead, and the pattern-matching code is just 400 old and battle-tested lines of C89.
Lua patterns have also shown up in other places, such as BSD's httpd, and an implementation for Rust:
https://www.gsp.com/cgi-bin/man.cgi?section=7&topic=PATTERNS
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/
What are some alternatives?
toml.io - Source Code for toml.io
json5 - JSON5 — JSON for Humans
jsonnet - Jsonnet - The data templating language
kdl - the kdl document language specifications
dhall-lang - Maintainable configuration files
yaml-reference-parser
minimal-yaml - A minimalist, zero-copy parser for a strict subset of the Yaml specification.
typescript-json-schema - Generate json-schema from your Typescript sources
yamllint - A linter for YAML files.
edn - Extensible Data Notation
Amethyst - Data-oriented and data-driven game engine written in Rust