Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Why not use XML? I guess there's not enough glory: it already exists and works!

    • by mpeters (5802) on 2009.03.12 6:45 (#67778) Homepage Journal

      Both JSON and XML are well established, fully specced and popular formats (XML more so, but there is a lot of JSON out there too). Picking one over the other should be based on a couple of key points where I think JSON far outshines XML:

      1) Like Alias said, which ever we pick needs to make it's way into the Core. For XML if we we'd need to pick a subset since a full XML parser is big and complicated. JSON in comparison is easy and simple. A JSON parser would be small and stand a better chance of making it into the Core.

      2) XML isn't really easy on the eyes and isn't a format that a lot of Perl programmers like. JSON looks very similar to the array/hash literal syntax that we are already used to and the simplicity is nice. No debating over whether something should be an attribute or a child element. It's just lists and hashes.