I can sacrifice that for a simple js oriented object notation improvement of JSON! I'll trade dashes in prop names all day for comments and trailing commas (and less quotes too). Of course it would break a gazillion existing schemas from people who enjoy such names... but I'd sacrifice that too haha 
Perhaps a middle ground is to allow quotes (like current JSON) for those pesky prop names?
Btw those quotes gave us several data points in db named "energy_consumption " (see the trailing space?) due to how fragile it is to write (in NR btw). Added a filter (also in NR) to prevent it (abort + log), so no more problem.
