Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Json has nothing to do with the persistence part.


If you need to persistently store frontend state in the backend, would it not be easier to use the native frontend data format?

It's not entirely about persistence... it's about the ease and reliability of the persistence.


My point is that that JSON isn’t being delivered via a js db but instead translated from data stored in a database written in C. So the “what about json” gotcha isn’t as good as it was made to seem.


My point is that JSON is being supported. So the "dismissal of facts" isn't as thoughtful as it was made to seem.


No it isn’t though? JSON is used, by developers, as an intermediary to exchange data pulled from a db. Your point that json is proof that the GP comment is false is not even a point but some kind of fallacy akin to a strawman.


Your inference of my intentions, as an intermediary to deflect from the facts presented, is proof that you're trying really hard to be edgy. Akin to a strawquant.

The people behind javascript provided the object notation technology that has been absorbed by Postgres. It is not only being used to exchange data (as a standard text field would be used), but can be used to QUERY data. The database is aware not only of the JSON text string representation, but of the object itself.


I’m not being edgy you took a data format and pretended it was a refutation when it wasn’t and isn’t.


What does the JS in JSON stand for? Where did it come from?


What does that have to do with JSON being an intermediary language and not the actual persistence part? What part of that don’t you understand and I’ll try to explain it for you


[flagged]


I understand perfectly the difference between a system and a format. You either don’t or you’re trolling (and dishing out ad hominems to boot.). Reddit would be more suitable to your posting style, we come here with a higher expectation of them being actual discourse and intellectual honesty.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: