tag:blogger.com,1999:blog-2420860529344694449.post7467566570981215063..comments2024-03-25T02:37:02.982-07:00Comments on Lin.ear th.inking: Is JSON the CSV of the 21st Century?Dr JTShttp://www.blogger.com/profile/02383381220154739793noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-2420860529344694449.post-59506141459866167242010-07-17T13:07:30.721-07:002010-07-17T13:07:30.721-07:00I've had good experiences running JSON through...I've had good experiences running JSON through a light compression algorithm. The data density is close enough to a binary representation for a lot of use cases and you get better separation of concerns. I really like the idea of human readable data formats. But they're certainly not free, and probably not right for all use cases. YAML has its own peculiarities. Like CSV, JSON has the major advantage of being stupidly simple.Unknownhttps://www.blogger.com/profile/03003237593537347060noreply@blogger.comtag:blogger.com,1999:blog-2420860529344694449.post-88014562213787364342010-07-09T12:25:18.683-07:002010-07-09T12:25:18.683-07:00Or should that be a paleo-protocol-programmer? 8^...Or should that be a paleo-protocol-programmer? 8^)Dr JTShttps://www.blogger.com/profile/02383381220154739793noreply@blogger.comtag:blogger.com,1999:blog-2420860529344694449.post-62288075212912075342010-07-09T12:22:50.431-07:002010-07-09T12:22:50.431-07:00That's a good perspective, Sean.
But does t...That's a good perspective, Sean. <br /><br />But does this preclude defining a scheme formalism for JSON for situations where it would be useful? That way the user can choose whether he wants to take the low road or high road for JSON use.<br /><br />Also, it seems to me that JSON is being used in many situations where there is NOT tight coupling - and they would hugely benefit from having a formal way of describing JSON schemas. (I guess I might say the same thing about the wider RESTful Web Service world in general...)<br /><br />From an SDLC perspective, the only situation I can see which doesn't *necessarily* require a formal specification is where a single person is defining both the client and server endpoints (and over a short time span!). That's pretty tight coupling indeed...<br /><br />But perhaps I'm just a paleoprogrammer... 8^)Dr JTShttps://www.blogger.com/profile/02383381220154739793noreply@blogger.comtag:blogger.com,1999:blog-2420860529344694449.post-60101406583409279592010-07-09T12:03:33.388-07:002010-07-09T12:03:33.388-07:00I disagree that JSON profits from schemas. Use XML...I disagree that JSON profits from schemas. Use XML instead for those applications. Use JSON where you can accept tight client-server coupling and treat it as dicts (Python) on the wire. Like you said: a more expressive take on CSV, one that happens to share some syntax with Javascript (and Python, and others).sgillieshttps://www.blogger.com/profile/04892958878143369551noreply@blogger.com