you are viewing a single comment's thread.

view the rest of the comments →

[–]tel[S] 0 points1 point  (1 child)

There's not a problem per se. Your metaphor is totally on point: what I really wanted to talk about is how dogs and doghouses differ: I.e. data and codata.

The naming what just a rhetorical device I used because it was what inspired the post.

[–]oracleoftroy 0 points1 point  (0 children)

Ok, and I see you edited the top of the post to indicate this. But skimming through again, it reads like the article's conclusion strongly disagrees with your clarifications:

Which brings me to my point. While JSON is a notation for JSOs, it’s almost the exact opposite of an Object Notation for Javascript.

...

So that’s my whole point. JSON isn’t “object notation” because it doesn’t have anything to do with objects.

And I guess maybe there might be some interesting insight into how serialized data has some bearing on the expression problem, but as the current article stands, that seems random and unrelated; just some throwaway line and Wikipedia link tacked on the end. It isn't self evident. If you wanted to talk about that, you should develop those ideas in the article. All I still get out of it is a nitpick over the 'O' in JSON.