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.
Dixy
-
JSON vs. XML with Douglas Crockford
I remember one time designing the simplest and most readable data format ever and came up with this https://github.com/kuyawa/Dixy after removing all I could and still make it usable
I'm leaving it here because it will never be used for anything but at least it may inspire somebody design a better format with simplicity in mind
- Dixy: Data Format Based on Dictionaries
-
Internet Object – A JSON alternative data serialization format
YAML and its "Arrays" are really broken. The problem I see with Internet Object is that it's also implying this kind of mechanism.
Every time I read about new formats, they seem to get either the 1-n relations or the n-n relations implemented well, but not both. I guess that's what's so hard about map/reduce...
Regarding YAML: somebody on HN mentioned his project DIXY a couple years ago, and it's much much _much_ easier to parse than YAML. [1] I'm using this over YAML pretty much everywhere now.
[1] https://github.com/kuyawa/Dixy
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?
zed - Rethinking code editing.
json - JSON for Modern C++
hujson - HuJSON: JSON for Humans (JWCC: JSON w/ comments and trailing commas)
EPOE-Forked - Github repository for EPOE-Forked
json5 - JSON5 — JSON for Humans
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
jsonschema-key-compression - Compress json-data based on its json-schema while still having valid json
yamllint - A linter for YAML files.
zed - A novel data lake based on super-structured data
dhall-lang - Maintainable configuration files
simdjson - Parsing gigabytes of JSON per second : used by Facebook/Meta Velox, the Node.js runtime, ClickHouse, WatermelonDB, Apache Doris, Milvus, StarRocks
json - A tested JSON parser / serializer