The arguments presented here would also lead someone to not use JSON for data interchange.

If specifying the schema is important then why not an interchange format with strict schema enforcement like XML?

If minimal feature sets to avoid abuse are so important, then why not a binary format like protobufs which also have strict schema dictates?

And if interoperability is important then why not ditch REST/JSON all together and instead favor SOAP which strictly defines how interoperability works?

That's why I don't buy the "comments might be abused" argument. JSON doesn't have a single problem domain and it's not the only solution in town.