this post was submitted on 05 Sep 2025
460 points (98.5% liked)

linuxmemes

27191 readers
905 users here now

Hint: :q!

Sister communities:

Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
    • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
    • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
    • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
    • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
    • Β 

    Please report posts and comments that break these rules!

    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    poopsmith@lemmy.world
    zephyr@lemmy.world
    rtxn@lemmy.world
    460
    An awkward realization (startrek.website)
    submitted 4 days ago by MalikMuaddibSoong@startrek.website to c/linuxmemes@lemmy.world
    77 comments fedilink hide all child comments
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] CheesyFox@lemmy.sdf.org 21 points 3 days ago (1 children)

    to be fair, out of those three, jq invokes the least existential dread in me

    [–] Tangent5280@lemmy.world 4 points 3 days ago (1 children)

    The important part is to learn the limits of any tool. Nowadays I no longer use jq for any long or complicated tasking. Filter and view data? jq is fine. Anything more and I just cook up a python script.

    [–] CheesyFox@lemmy.sdf.org 5 points 3 days ago (1 children)

    i'm more of a bash fan tbh. Ever since i started using linux, python started to irritate me

    [–] Tangent5280@lemmy.world 4 points 3 days ago (1 children)

    How do you get complex data structures to work? I was alienated from scripting on zsh because I wanted something like a dict and realised I would have to write my own implementation. Is there a work around for that?

    [–] tal@lemmy.today 6 points 3 days ago* (last edited 3 days ago) (1 children)

    I mean, there's a point in data structure complexity where it's useful to use Python.

    But as to dicts, sure. You're looking for zsh's "associative array". Bash has it too.

    zsh

    $ typeset -A mydict
$ mydict[foo]=bar 
$ echo $mydict[foo]
bar
$

    bash

    $ typeset -A mydict
$ mydict[foo]=bar
$ echo ${mydict[foo]}
bar
$
    [–] Tangent5280@lemmy.world 4 points 3 days ago

    This will do nicely - I had several workflows where I'd hit an API and get a massive super nested JSON as output; I'd use jq to get the specific data from the whole thing and do a bunch of stuff on this filtered data. I pretty much resigned to using python because I'd have successively complicated requirements and looking up how to do each new thing was slowing me down massively.