Beefy Boxes and Bandwidth Generously Provided by pair Networks
good chemistry is complicated,
and a little bit messy -LW
 
PerlMonks  

Re: JSON or XML?

by Tanktalus (Canon)
on Apr 25, 2012 at 19:25 UTC ( #967154=note: print w/ replies, xml ) Need Help??


in reply to JSON or XML?

tye introduced me to JSON via the CB some years ago. It has become the lingua franca here. Everything we transmit from one app to another is going either through a database (SQL) or JSON. XML exists, but only with third-party apps that we don't control, and, for the most part, we don't interact with them through their XML anyway. JSON has a simpler API for both encoding data and extracting data. And that simpler API is language-agnostic: join '', map { "Using JSON in $_ is easier than using XML in $_.\n" } qw( Perl Java JavaScript ActionScript ) And both are downright horrible in shell script. So we don't do that.

JSON also is less verbose. Which makes it better suited for tracing inputs/outputs in our trace files. (When objects are involved, it becomes a bit tricky, but XML serialisation has the same issue.) Our trace files grow fairly big fairly quickly already, keeping bloat down is always a win.


Comment on Re: JSON or XML?
Download Code

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://967154]
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (13)
As of 2014-09-23 16:05 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    How do you remember the number of days in each month?











    Results (228 votes), past polls