I hope you're joking.
Why? It's a valid solution.
Mixing metadata in with data isn't ideal.
Mixing metadata with a serialization format isn't ideal. Want metadata? Use a markup language.
Actually it is. Then you can treat them the same way.
And since it's a configuration format, you know what keys are accepted and what keys are for the metadata, and thus won't clash.
But metadata is also data.
this is what is recommended for package.json in node. Specially "//" as the key.
config = { "version": "1.0", "comment": "JSON has comments too!" }