41
How are you parsing JSON on the command line?
(lemmy.world)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 12 Jun 2024
41 points (97.7% liked)
Linux
48463 readers
1032 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
What are some goos resources for learning jq? I really struggle when it comes to nested keys/values which obviously limits my ability to use it.
Online json parser. Throw in some data and then structure a query.
It'll keep updating the results as you tweak your query. A simple search will probably give you twenty that'll work. I can't remember what i normally use off the top of my head.
man jqI have perused it, but its both so dense and so broad that its not that helpful unless i know exactly what I'm looking for. I have also tried info and tldr. I actually like tldr the most,. although the exhaustiveness of the man pages must be admired. I dont find it to be the best teacher.
I hate to do this, but AI chatbots are typically pretty good at giving examples for things like this and you can learn from it.
AI chatbots are very good for teaching. I'll give them that.
I definitely use them a lot, but I think "very" is too strong a word. It's pretty easy to get confident, contradictory information from them. They're a good place to start and brainstorm, but all the information has to be verified either by running and testing the code, or by finding a human source.
True. I wouldn't use them for very complicated stuff. I currently use them for "what is x?" and "how is x different from y?" kinds of question.
One advantage of using an AI is that it removes a lot of fluff that you get on blogs. However, that can change very soon when our AI overlords figure out monetization.