After watching this video, I’m tempted to give it a try myself. The idea of swapping out traditional CLI tools for Rust-based alternatives is intriguing, and I’m curious to know if anyone has undertaken such an endeavor.

I’m also on the lookout for dotfiles that primarily feature configurations for Rust tools. I find it both educational and entertaining to explore other people’s configurations. I stumbled upon this repository, but I’m interested in discovering more if possible.

  • dino@discuss.tchncs.de
    link
    fedilink
    English
    arrow-up
    1
    ·
    8 months ago

    nu is probably the best shell for ad-hoc data processing, handling all my daily needs in one expression.

    I am really struggling with this, I heard about nu shell some time ago, but the fact that you had to learn some form of new language made me reluctant to actually try it. As a fisher user I want to have sane usable defaults, without having to learn just another programming language for a “tool”.

    What am I missing?

    • Spore@lemmy.ml
      link
      fedilink
      arrow-up
      2
      ·
      edit-2
      8 months ago

      It kinda fills a niche.

      I use fish for simple command pipelines as well. But traditional shells are not as good when I need to do anything “structured”, because they treats almost any value as a string and don’t have anonymous functions. The first problem means that you have to parse a string again and again to do anything useful, the second means that when both pipe and xargs fails you are doomed.
      Nu solves both of the big problems that matters when you want to do rather complex but ad-hoc processing of data. And with a rather principled design, nu is very easy to learn (fish is already way better than something POSIX like bash though).

      Personally another important reason is that I have a Windows machine at work and nushell is much easier than pwsh.

      Btw fish is also going to be a “tool in rust” soon :)