Our great sponsors
hjson-js | edn | |
---|---|---|
9 | 34 | |
404 | 2,567 | |
0.5% | 0.7% | |
0.0 | 0.0 | |
2 months ago | over 2 years ago | |
JavaScript | ||
MIT License | - |
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.
hjson-js
-
[OC] No comments
By the way.. if you use the hjson parser you can add comments to json files :) https://hjson.github.io/
- YAML vs. JSON
-
In a symfony interview I got asked "but why json? XML is better"
I wish this took off https://hjson.github.io. I like it much more than yaml.
-
policy generator?
I don't know anything about VueJS either but HJSON is pretty cool in that regard https://hjson.github.io/
-
Keeping documentation in sync with source code
> Another difficult problem was checking for correct indentation visually (because the configuration is YAML-based and indentation matters).
why yaml? I hate it so much! my eyes hurt looking at it?
why not using https://hjson.github.io/ ?
-
JSON5 Data Interchange Format
HJSON [0] is also another format that tries to make it easier for humans to read / write json.
[0] https://hjson.github.io/
-
YAML and Configuration Files
well there are json alternatives which fit this bill, such as HJSON.
https://hjson.github.io/
might not be as "common" but it has good implementations for many languages.
-
zdpack - A tool for merging and converting Minecraft data and resource packs.
zdpack also pre-processes datapacks, allowing json files to be written in hjson or yaml, in addition to allowing a special extensible super-set of MCFunction I call CommandScript. You can check the github page for a quick overview of CommandScript.
- The Goals of XML at 25: and the one change that XML now needs
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?
Lowdb - Simple and fast JSON database
json - JSON for Modern C++
json5 - JSON5 — JSON for Humans
EPOE-Forked - Github repository for EPOE-Forked
Knex - A query builder for PostgreSQL, MySQL, CockroachDB, SQL Server, SQLite3 and Oracle, designed to be flexible, portable, and fun to use.
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
NeDB - The JavaScript Database, for Node.js, nw.js, electron and the browser
yamllint - A linter for YAML files.
buckets - A complete, fully tested and documented data structure library written in pure JavaScript.
dhall-lang - Maintainable configuration files
schemapack - Create a schema object to encode/decode your JSON in to a compact byte buffer with no overhead.
json - A tested JSON parser / serializer