benchmarks

> b) do you have speed tests to show your libraries are better than existing ones? The OP linked to their benchmarks in [3]: https://github.com/eno-lang/benchmarks/

The `benchmarks` repo contains various sample files in yaml, toml and eno https://github.com/eno-lang/benchmarks/

eno [1] - A modern plaintext language w/ libraries [2] for JavaScript, Python, Ruby & soon more! We migrated a big relational research database to a file-based solution - requirements were: - Super fast and easy editability for users - Highest performance for parsing/validating >10K documents on every user change. Our trials with YAML/TOML showed us that we wanted something both faster [3][4] and easier [4], something tailored for file-based content management ... and after months of research & development it's now publicly available (under MIT license) for everyone! Last but not least I also want to mention eno's document introspection capabilities - with a few lines of code you can build intelligent relational suggestion UIs as shown in [4] below. [1] https://eno-lang.org/ [2] https://eno-lang.org/libraries/ [3] https://github.com/eno-l