@brunty I think they all have their place. Coders love #JSON because it looks like code (non-coders hate it for the same reason). #YAML is great for config files, but gets awkward for more-advanced data. Nobody loves #XML, but I find that non-coders hate it slightly less than JSON, just because it looks a bit like HTML (many more people know HTML than know how to write code) and handles mixed content elegantly.
Still, complex data is complex, regardless of the representation.
@brunty OK, I'll admit, I love #XML too: I wrote two books about it and was a member of the original #W3C XML WG and chaired the XML Core WG afterwards. 🙂
But all the same, when I was chairing XML 2007, I did invite @douglascrockford to give a closing keynote about #JSON, just to remind the aficionados that there was more to #markup than XML.
A community member is looking for #codereview on a #JSON log formatter for #Python. Is this approach sound? You can post an answer addressing some or all of the (small) body of code shown; this isn't conventional Q&A where you need to have "the answer". Can you help? https://software.codidact.com/posts/288091
New post: Improving my interactive #jq workflow with ijq, #bash and #tmux.
I'm a big fan of ijq and how it allows me to explore #JSON data interactively with jq expressions. With a small script I have improved my workflow by being able to capture the jq expression from ijq and use it easily on the command line.
What do you do when you need to inspect HTML, XML, JSON, or a JWT while debugging? 🐞
.
.
.
👀
.
.
.
Use Rider 2023.1's new debugger visualizers of course!
This is hilarious. A #Google engineer invented #zx to make command line scripting easier with #NodeJS, because at a certain point #shell scripts get too complicated and you need a Real #Programming Language.
This is exactly #Perl’s use case from thirty-six years ago. But the kids want #JavaScript everywhere and would rather it take more work to convert their ascended #Bash scripts to a vastly different syntax.
@ndw Reading your bio. I’m almost reluctant to point out that the same “worse is better” cycle applies to #markup languages. #JSON was a reaction to #XML, #Markdown was a reaction to #HTML, and both have since acquired layers to add back what they threw away.