• flying_sheep@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    4 hours ago

    Idk if that’ll make you happy. The different POSIXy shells have so many subtle differences and footguns that I personally feel best

    • using nushell as a daily driver, as it’s sane and makes sense and errors out when it should
    • using bash when forced to interact with things that are written in bash (I don’t know anything written in fish or ZSH)
    • using Python or Rust or so for scripts living in projects that are written in that language

    I can’t be bothered to look up the weird arcane sigils that make bash not shit itself when e.g. using arrays as command args or so, so I will author only the most pedestrian bash scripts where pipes are already a bit much.

    • TehPers@beehaw.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      3 hours ago

      I already do #1, and I push for #3 (specifically Python or TS) where I can at work, but there’s this weird obsession with bash that people have at work despite all these scripts not running on Windows natively (outside WSL). Currently I do #2, but I often end up just stuck in bash the whole time because it’s needed for things as simple as building our code. I want to try out Fish as an alternative for those situations.