It looks like the latest version of the org.json library no longer supports
comments. This is technically correct (JSON does not define comments), but
it does make JSON less useful as a configuration language.
The PHP code has a similar limitation, and it was hacked around by only
stripping /* */ style comments (everywhere) and // style comments (with an
exception for cases where it is immediately prefixed with http:, https:, or
a double quote ("//)
This kind of works, but it's all very hacky and fragile (file:// and other
references would have to be tacked on as well).
We could implement our own JSON parser, but I don't think this is the right
approach given that comments aren't actually a part of the spec.
I was thinking about swapping out the json container configuration files
with YAML instead. This has the benefits of JSON, but in a language that was
actually designed with configuration in mind.
