I recently came a cross a blog talking about JSON, a straight forward alternative to XML. I’ve always disliked XML, and so has pretty much everyone I’ve ever known who’s had to muck with it. It’s not terrible, just clunky, and seems so much less efficient than the one-off csv type files most of the unixy folks I associate use. JSON tries to combine the two, but has easy-to-read, simple, lightweight, and yet is standard and portable. How cool is that?
From www.json.org’s description:
Extensible Markup Language (XML) is a text format derived from Standard Generalized Markup Language (SGML). Compared to SGML, XML is simple. HyperText Markup Language (HTML), by comparison, is even simpler. Even so, a good reference book on HTML is an inch thick. This is because the formatting and structuring of documents is a complicated business.
Most of the excitement around XML is around a new role as an interchangeable data serialization format. XML provides two enormous advantages as a data representation language:
- It is text-based.
- It is position-independent.
These together encouraged a higher level of application-independence than other data-interchange formats. The fact that XML was already a W3C standard meant that there wasn’t much left to fight about (or so it seemed).
Unfortunately, XML is not well suited to data-interchange, much as a wrench is not well-suited to driving nails. It carries a lot of baggage, and it doesn’t match the data model of most programming languages. When most programmers saw XML for the first time, they were shocked at how ugly and inefficient it was. It turns out that that first reaction was the correct one. There is another text notation that has all of the advantages of XML, but is much better suited to data-interchange. That notation is JavaScript Object Notation (JSON).
The most informed opinions on XML (see for example xmlsuck.org) suggest that XML has big problems as a data-interchange format, but the disadvantages are compensated for by the benefits of interoperability and openness.
JSON promises the same benefits of interoperability and openness, but without the disadvantages.
Let’s compare XML and JSON on the attributes that the XML community considers important.
Here’s a neat example of some jason formatted data:
{
"firstName": "John",
"lastName": "Smith",
"address": {
"streetAddress": "21 2nd Street",
"city": "New York",
"state": "NY",
"postalCode": 10021
},
"phoneNumbers": [
"212 555-1234",
"646 555-4567"
]
} |
I landed at JFK at about four. By the time I got to my hotel on 29th St. in Manhattan, it was five thirtyish. After flopping on the bed and taking a shower to wash the travel off, I needed a bite to eat. There’s a decent deli on the corner that sells pizza by the slice, but they were closing up by the time I got there. I remembered seeing a burger place a few blocks away the last time I was here, and it had looked decent, so I headed off in the general direction hoping it was where I remembered.
some mixed reviews on citysearch… I guess overall, I’d say if you happen to be walking by and are hungry, it’s probably worth stopping in, but definitely not worth crossing town. My one regret is I noticed after I ordered that they had egg as a condiment, and bacon and and an over easy egg are two great toppings for a burger.
on group as directed the more well known 
Overall, I think Kai Do Maru is good, but not great. I did like that it’s an unapoligetically grownup film, and the artwork is certainly interesting, and debatably beautiful. At 45 minutes, it feels right, any more and it might be too much, any less and it would be unsatisfying. Watch it via netfix’s watch now feature and you won’t be disssapointed, but don’t plan an evening around it.