node-jsonc-parser
hjson
node-jsonc-parser | hjson | |
---|---|---|
4 | 5 | |
555 | 2,625 | |
0.9% | 0.3% | |
4.2 | 4.8 | |
3 months ago | 13 days ago | |
TypeScript | HTML | |
MIT License | 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.
node-jsonc-parser
-
The real reason JSON has no comments
Well, there is JSONC for those who do want those comments
-
We need a JSON 2
When you say .jsonc, do you mean JSONC, JSONC, or JSONC? And have I mentioned JSON-C?
-
Vue is actually pretty good
and im not sure if i agree with the comments bit. "very basic extendable base" is very good place for a format to be imo. need comments? add em, like microsoft did.. the YAML sotuation again.
- microsoft/node-jsonc-parser
hjson
-
Why the fuck are we templating YAML? (2019)
HJson https://hjson.github.io seems a nice 'in-between' between YAML and JSON without the indentation-based syntax, so closer to the JSON side but with comments and less quotes.
What I don't really get is why the cloud providers / tooling implementors have never drafted up a "YAML-light" that just throws out the rarely-used headache-inducing syntax elements.
-
That's a Lot of YAML
Hjson is very similar to JSON5 but allows quotes to be dropped and can use newlines instead of commas. There are implementations for a lot of different languages, I myself contributed the C++ implementation. I wanted something smaller than Yaml but more lax than JSON, found Hjson to suit my needs perfectly.
https://hjson.github.io/
-
The real reason JSON has no comments
JSONs make terrible config files. If you want to use json-like syntax for config, use hjson instead. It's basically json, but changes it slightly so it better matches human expectations.
-
The YAML Document from Hell
```
YAML and JSON succeeded because they had a clean and predictable, no-nonsense mapping between encoding and object-model after decoding. Probably we should all switch to an almost-yaml format that does away with the peculiarities, and the FANG companies would have the momentum to make that happen.
I personally would like for HJSON (https://hjson.github.io) to see more adoption, but that train has passed...
-
Why?
There’s also json-c and Hjson.
What are some alternatives?
jsonc - json like config with comments.
noyaml - A silly emotional rant about the state of devops tooling/the infrastructure sector in 2018. #noyaml.com