yq
edn
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.
yq
- Jaq – A jq clone focused on correctness, speed, and simplicity
- jq 1.7 Released
- Using XPath in 2023
-
How to troubleshoot yaml parsing error "did not find expected key"?
Install jq and yq, and wrap your commands with | yq -y ..
-
Memes are all cool and all. But this is your daily remaining that 10000! =
Confusingly there is another project called yq that does exactly what you're suggesting and it's a preprocessor that converts yaml to json and then used jq. https://github.com/kislyuk/yq
-
inhumane and error-prone
yq
-
Yq is a portable yq: command-line YAML, JSON, XML, CSV and properties processor
I personally find the yq tool from https://github.com/kislyuk/yq much more useful: it has all the same options and formats as `jq` (as it's really a wrapper around jq). Rather than the `yq` in the OP here where only partial functionality exists.
- The YAML Document from Hell
-
Scraping weather info
XML data from the API can be parsed and filtered with xq. There may be multiple ways to get it; first try the yq toolset which includes it.
-
Show HN: Xq – command-line XML and HTML beautifier and content extractor
There is also yq [1], which attempts the same for yaml, toml and xml. (And confusingly also contains a binary named "xq" for querying xml, however with a different syntax)
[1] https://github.com/kislyuk/yq
edn
-
Apple releases Pkl – onfiguration as code language
> was utterly surprised how no one ever apparently has thought to create a configuration/templating system that's basically a fancy library on top of Scheme.
There's Clojure's extensible data notation: https://github.com/edn-format/edn
- Why the fuck are we templating YAML? (2019)
-
I made a basic python client and ORM for XTDB
A thin language layer around edn/datalog, the query language
-
What Is Wrong with TOML?
EDN (Extensible Data Notation) is a subset of Clojure: https://github.com/edn-format/edn
It is:
- Streamable
- Extensible
- Whitespace-insensitive, but there are formatting conventions for readability
-
The real reason JSON has no comments
To begin with, EDN is somewhat like the JSON of Clojure. And regarding the code is data/data is code nature of Clojure, it is Clojure. It doesn't have some of the vagaries of JSON, and it is also extensible.
-
Ron: Rusty Object Notation
Alien is not a reason something is bad, just that's it's unusual. JSON was a bit alien when it first arrived as well, as everyone was used to XML at the time.
`{num 5, val 4}` looks fine to me, but we can do even better! We already know objects/maps are always in pairs, so we don't really need that comma either. Just do `{num 5 val 4}` and we save yet another unnecessary characters.
Of course, I didn't come up with this format myself, what I actually want JSON to be is EDN (https://github.com/edn-format/edn) which is a standalone format but also directly used in Clojure, so it already exists inside a programming language and works very well. There keys are strings though, so you example would end up being `{"num" 5 "val" 5 "person" var}`, where commas are optional.
-
JSON vs. XML with Douglas Crockford
I just checked out the spec, and it gets pretty ugly in the Table section. A lot of the json examples are both shorter and IMO more precise. Stuff that’s not allowed with [table] is allowed with [[table]], and it’s confusing to understand what level of depth I’m at.
I’ll take edn over any of “em. https://github.com/edn-format/edn
-
Taming the Time: how to install & develop with XTDB
As XT is written in Clojure and it natively supports Clojure’s data types, we were not satisfied with available JSON types and decided to give EDN a try - that way we would have way more supported types:
-
Design patterns are a solution to the problem OOP itself creates
Compare the nightmare that is pickling with how simple it is to serialize pure data with edn in clojure. What ends up happening is people passing around JSONs or whatever and writing parsing/encoding code at each end, which makes things unnecessarily more complex, and dangerous, and error prone, and boring, etc...
- The YAML Document from Hell
What are some alternatives?
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
json - JSON for Modern C++
yq - yq is a portable command-line YAML, JSON, XML, CSV, TOML and properties processor
EPOE-Forked - Github repository for EPOE-Forked
jq - Command-line JSON processor
dasel - Select, put and delete data from JSON, TOML, YAML, XML and CSV files with a single tool. Supports conversion between formats and can be used as a Go package.
yamllint - A linter for YAML files.
xmlq - filter xml in the command line with xpath
dhall-lang - Maintainable configuration files
hn-search - Hacker News Search
json - A tested JSON parser / serializer