This is interesting, but I still find HJSON a better "JSON for humans format". HOCON seems to mix in things that better belong in the consumer, not the objection notation format.
I would say HOCON isn't JSON for humans, it's config file for humans. The features are all about building up a config in a DRY way and merging overrides with defaults and overriding with env vars and stuff like that. It's specifically for the config use case.
JSON superset is a bonus feature which is useful if you don't want to learn new syntax or want to machine-generate part of your config.
