• kosmoz@beehaw.org
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    Fish (suggested by the article as well) is amazing. Also:

    • bat (better cat),
    • btm (better top),
    • httpie (better curl),
    • ripgrep (better grep),
    • zoxide (cd with fuzzy search)
    • jq (for manipulating JSON)

    But honestly, lots of classics are still great: git, htop, rsync, vim, nano, …

    • comicallycluttered@beehaw.org
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Hello, fellow fish user! Oh, shit, am I doing the Arch thing?

      Will have to check some of those other ones out.

      I’ve personally replaced nano with micro, though. Find it much friendlier to use.

      • maynarkh
        link
        fedilink
        English
        arrow-up
        5
        ·
        1 year ago

        Real programmers cat the data directly from /proc

    • MangoPenguin@lemmy.blahaj.zone
      link
      fedilink
      English
      arrow-up
      2
      ·
      1 year ago

      Personally I find btop really hard to glance at and see what’s happening, htop is much better for opening up and quickly checking what process is hogging CPU/RAM/IO/whatever.

  • flakusha@beehaw.org
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 year ago

    Be careful not to replace bash with fish as some systems fail to work with new shell. I usually init fish/nu shells with other instruments, like alacritty and/or zellij