foss

  • jsdz@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    "bat" seemed interesting, until I remembered that I'd just do a "git diff" if I wanted to see a diff. The rest do not strike me as substantially better than what they're trying to replace. Enjoy them all as you will, but I would recommend refraining from describing them as "modern unix" in the presence of any old-timers.

    • Pantherina@feddit.de
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      Bat also adds lots of stuff to the output. Is there a clean print functionality without the extra numbers?

      Edit: but with the parameters its great!

    • jellyfish@sh.itjust.works
      link
      fedilink
      arrow-up
      1
      ·
      edit-2
      1 year ago

      Quite a few are just better, and others have the chance to get better because they're actively accepting new features contributions.

      One I personally use:

      • delta Provides a better diff for code than git's diff tool (even after trying all of git's diff algorithms)
      • ripgrep So much faster than grep. Also had great include/exclude file filtering, easier to use than grep's
      • jq Easy to exact json info. I tend to use rq too for yaml
      • instead of mcfly I use atuin, which is another alternative bash history. I really didn't think I'd like it, but it's been a big productivity boon
      • curlie/httpie A really nice alternative to something like postman when debugging HTTP connections. I use httpie rn but might switch because I'm so much more familiar with curl's flags, but like the formatted output. There's a few others I use that aren't on the list too.

      It's totally fine to not want to change what's working for you, but if you do that too long you could miss out on something that just works better in your workflow. Give em a go and complain after you switch back.