Not a fan http://hjson.org . JSON’s syntax is strict and not feature-full because JSON is meant to be generated, not written by hand
-
-
Replying to @oscargodson
The more complex you make JSON, like HJSON, you will without a doubt come into numerous edge cases and different handling between parsers
1 reply 0 retweets 1 like -
Replying to @oscargodson
@oscargodson agreed - cool thing about JSON is that it's well understood and not overly complex; breaking that is
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts Like multiline strings and the fact comments can start /*, //, or #. All of those complicate the parser significantly1 reply 0 retweets 1 like -
Replying to @oscargodson
@oscargodson I think TOML took the right approach here - take the essence (nested hash maps) and design from scratch - probably works better1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
@yoshuawuyts TOML is a nice looking format. It’s still super complicated parsing wise: https://github.com/BinaryMuse/toml-node/blob/master/lib/parser.js … vs https://github.com/douglascrockford/JSON-js/blob/master/json_parse.js …1 reply 0 retweets 0 likes -
Replying to @oscargodson
@oscargodson oh, hahaha that's mad! Though I guess it's trade offs right; probably still simpler than YAML? Def diff use case than JSON (':1 reply 0 retweets 1 like -
Replying to @yoshuawuyts
@yoshuawuyts oh yeah for sure. That just looks more like a “config file for humans to read”. JSON is like a format for servers to read1 reply 0 retweets 1 like
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.