Add json as a configuration file type about imagr

[gregneagle]

Disagree. JSON maps fairly well to plists, but it's not perfect. For example, there's no canonical way to represent a date in JSON, or distinguish between integers and floats (they are all numbers).

This tool is for managing OS X and should use OS X's native structured data representation. Supporting JSON and plist formats will just add code complexity.

[keeleysam]

plistlib is widely available as part of the standard Python library on
every operating system since 2.6.

I believe that JSON would confuse more than it could help.

On Wed, Apr 22, 2015 at 9:10 PM, Greg Neagle [email protected]
wrote:

Disagree. JSON maps fairly well to plists, but it's not perfect. For
example, there's no canonical way to represent a date in JSON, or
distinguish between integers and floats (they are all numbers).

This tool is for managing OS X and should use OS X's native structured
data representation. Supporting JSON and plist formats will just add code
complexity.

—
Reply to this email directly or view it on GitHub
#27 (comment).

Samuel Keeley

[grahamgilbert]

Python, Ruby and Node.js all have the ability to read and write plists, so I'm going to stick with plists. I've written apps that serve plists with Python before that worked fine (Sal+).

[natewalck]

Ok, thats cool. I was just hoping to get some diversity here, especially when considering other environments. json is pretty much the standard for getting data back from a web API and therefore if you are integrating with other systems that are using web standards, this could make it easier, whereas plists are pretty unique to OS X.