I agree that from a completeness point of view, the official manual is better (I’ve linked it at the bottom of my post as well), however I’d love to hear your specific thoughts about why you feel this particular article is not good- I’ve tried to include fully interactive examples for the most common tasks I find myself doing with jq everyday. This feedback will help me improve my own skills as well, so I would appreciate it very much.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: !programming@programming.dev
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person’s post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
Follow the programming.dev instance rules
Keep content related to programming in some way
If you’re posting long videos try to add in some form of tldr for those who don’t want to watch videos
I agree that from a completeness point of view, the official manual is better (I’ve linked it at the bottom of my post as well), however I’d love to hear your specific thoughts about why you feel this particular article is not good- I’ve tried to include fully interactive examples for the most common tasks I find myself doing with
jqeveryday. This feedback will help me improve my own skills as well, so I would appreciate it very much.I thought it was great in terms of listing examples for common use cases and I appreciated that the commands could be altered and ran interactively.