hjson

Unquoted strings that are valid numbers or booleans are parsed as those types when unmarshalling to interface{}, potentially causing unintended data types unless using typed destinations, as warned in the README.

To read comments, you must use hjson.Node as the root destination, which adds complexity with a different data structure (e.g., OrderedMap) and convenience functions, unlike standard Go types.

While it has a CLI tool, many third-party tools and libraries in the Go ecosystem assume standard JSON, potentially requiring conversion steps or limiting seamless integration.

The extended syntax requires more complex parsing than standard JSON, which might introduce slight performance penalties in high-throughput scenarios, though it's optimized for human readability.