Bobinas P4G
  • Login
  • Public

    • Public
    • Groups
    • Popular
    • People

A table mapping the term "json" to possible meanings: JavaScript Object Notation a human-readable data format combining arrays and key-value pairs the magic needed to get websites and API endpoints to give you useful data unstructured, but at least it doesn't make you yaml thankfully unentangled from JavaScript the illusion of superiority to plain text, but you still need to know the structure and have to parse the whole damn thing before you can process fields a data format that requires at least 5 attempts to extract a nested field using jq(1) because, honestly, '.who[].remembers|{(.the) \"syntax\"}' the reason you're somehow still in love with jq(1) "_comment" : "oh that makes a lot of sense" # it really doesn't, tho Expected another array element at line 2359, column 117 seriously, you can't handle a trailing comma?! still often better -- a lot better -- than the alternatives

Download link

https://media.mstdn.social/media_attachments/files/110/391/826/671/589/816/original/f3bfd11573a45042.png

Notices where this attachment appears

  1. Jan Schaumann (jschauma@mstdn.social)'s status on Thursday, 18-May-2023 22:29:08 UTC Jan Schaumann Jan Schaumann
    in reply to

    The secret language of coders, part N of many. Today: "json"

    In conversation Thursday, 18-May-2023 22:29:08 UTC from mstdn.social permalink
  • Help
  • About
  • FAQ
  • Privacy
  • Source
  • Version
  • Contact

Bobinas P4G is a social network. It runs on GNU social, version 2.0.1-beta0, available under the GNU Affero General Public License.

Creative Commons Attribution 3.0 All Bobinas P4G content and data are available under the Creative Commons Attribution 3.0 license.