LGV_MeetingServer
ron
| LGV_MeetingServer | ron | |
|---|---|---|
| 2 | 24 | |
| 1 | 3,146 | |
| - | 2.2% | |
| 6.5 | 7.6 | |
| about 1 month ago | 16 days ago | |
| PHP | 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.
LGV_MeetingServer
-
XML is better than YAML
I find “self-documentation” often doesn’t actually work. It’s great in theory, but often falls down, in practice.
I often need to preface my config stuff with fairly substantial comment blocks that discuss the reasoning behind the configuration.
Here’s an example: https://github.com/LittleGreenViper/LGV_MeetingServer/blob/m...
-
How to Write a Great Readme
I generally have a “What Problem Does This Solve?” section in my READMEs.
https://github.com/LittleGreenViper/LGV_TZ_Lookup#what-probl...
https://github.com/LittleGreenViper/LGV_MeetingServer#what-p...
https://github.com/RiftValleySoftware/RVS_Spinner#what-probl...
https://github.com/RiftValleySoftware/RVS_BlueThoth#what-pro...
https://github.com/RiftValleySoftware/RVS_PersistentPrefs#wh...
etc.
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.
-
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
- Ron – Rusty Object Notation
- They're rebuilding the Death Star of complexity
What are some alternatives?
keep - The open-source alert management and AIOps platform
toml.io - Source Code for toml.io
yaml-sucks - YAML sucks.
json5 - JSON5 — JSON for Humans
RVS_PersistentPrefs - A Simple Class For Basic Persistent Storage
kdl - the kdl document language specifications
uplaybook - A python-centric IT automation system.
minimal-yaml - A minimalist, zero-copy parser for a strict subset of the Yaml specification.
nix-configs - My Nix{OS} configuration files
yaml-reference-parser
undb - 🚀 Private first, unified, self-hosted no code database.
typescript-json-schema - Generate json-schema from your Typescript sources