command-line-rust VS fd

You absolutely must write programs, preferably using tests to ensure you are creating correct and reproducible code. May I suggest starting with my book, Command-Line Rust (O'Reilly, 2022). All the code/data/tests are in https://github.com/kyclark/command-line-rust Note that there are branches showing how to use the 4.x version of clap (command-line argument parser) rather than the 2.33 that was current when the book was published.

I think the best way to start learning a programming language is to write lots of small programs that you probably already know. Rust is a perfect command-line language, so I think it makes sense to start by implementing simple programs like "head" and "grep." I also think one should always learn to write and run tests, so I present my GitHub repo of inputs and tests you might like to use to write 14 such standard Unix command-line utilities: https://github.com/kyclark/command-line-rust If you want guidance on the language, I wrote a book called Command-Line Rust (O'Reilly, 2022) that explains all this code. One caveat is that the "clap" (command-line argument parser) module was at 2.33 when I published but is now v4, so you should look at the appropriate branches for versions of the programs that use the "builder" and "derive" patterns for that module. Or just use any old command-line parser you like as there's no requirement to use "clap." Best of luck to you!

You must write programs in a language in order to learn it. I also firmly believe that learning how to write and run tests is critical to learning any language. I wrote Command-Line Rust (O'Reilly, 2022) for the beginner (in Rust, at least) and with a focus on writing and testing small programs from very simple "Hello, world!" and getting increasingly more complex. You can look at https://github.com/kyclark/command-line-rust for the code/inputs/tests. Best of luck!

Code for the above book

I'm the author of Command-Line Rust (O'Reilly, 2022), which I wrote to introduce the language slowly to beginners by writing and testing short, focused programs. You can look over the code/tests/data at https://github.com/kyclark/command-line-rust. Note that there are branches that show the same programs using a more recent version of the "clap" crate.

I wrote Command-Line Rust (O'Reilly, 2022) to guide beginners in the language. You are challenged to write small functions and programs using tests to verify that everything is correct. You can look over the code and tests at https://github.com/kyclark/command-line-rust. Best of luck in your journey!

Here are the example programs from my book, Command-Line Rust (O'Reilly, 2022), along with the input files and tests: https://github.com/kyclark/command-line-rust

I like to suggest that students write programs they already know (or at least understand). For instance, you probably understand that head shows the first few lines of a text file, and you probably can already implement some version of that in one or two languages you know. Try that in Rust. I wrote 14 BSD/GNU command-line utilities in Rust for learning purposes. I wouldn't consider these high-performance/production programs as they are tailored to learning the language. I also stress how to test programs, so there are tests and inputs you can use to verify your programs match the output of the original programs (or you can modify these to suit your own tastes for how you would like them to work). https://github.com/kyclark/command-line-rust

Here are some more examples you may or may not find useful: https://github.com/kyclark/command-line-rust I tend to have a main() that calls a library's run() function that returns a Result and then exit with a nonzero code and error message on a failure.

ripgrep: A super-fast file searcher. You can install it using your system's package manager (e.g., brew install ripgrep on macOS). fd: Another blazing-fast file finder. Installation instructions can be found here: https://github.com/sharkdp/fd

hyperfine is such a great tool that it's one of the first I reach for when doing any sort of benchmarking.

I encourage anyone who's tried hyperfine and enjoyed it to also look at sharkdp's other utilities, they're all amazing in their own right with fd[1] being the one that perhaps get the most daily use for me and has totally replaced my use of find(1).

[1]: https://github.com/sharkdp/fd

You call it with `n` and get an interactive fuzzy search for your directories. If you do `n ` instead, it’ll start the find with `` already filled in (and if there’s only one match, jump to it directly). The `ls` is optional but I find that I like having the contents visible as soon as I change a directory.

I’m also including iCloud Drive but excluding the Library directory as that is too noisy. I have a separate `nl` function which searches just inside `~/Library` for when I need it, as well as other specialised `n` functions that search inside specific places that I need a lot.

¹ https://github.com/sharkdp/fd

² https://github.com/junegunn/fzf

Many (most?) of them have been overhauled with success. For find there is fd[1]. There's batcat, exa (ls), ripgrep, fzf, atuin (history), delta (diff) and many more.

Most are both backwards compatible and fresh and friendly. Your hardwon muscle memory still of good use. But there's sane flags and defaults too. It's faster, more colorful (if you wish), better integration with another (e.g. exa/eza or aware of git modifications). And, in my case, often features I never knew I needed (atuin sync!, ripgrep using gitignore).

1 https://github.com/sharkdp/fd

Descubra mais sobre o fd em: https://github.com/sharkdp/fd

AFAIK there is a find replacement with sane defaults: https://github.com/sharkdp/fd , a lot of people I know love it.

However, I already have this in my muscle memory:

fd

> without zsh globs I have to remember find syntax

My "solution" to this is using https://github.com/sharkdp/fd (even when in zsh and having glob support). I'm not sure if using a tool that's not present by default would be suitable for your use cases, but if you're considering alternate shells, I suspect you might be

Nice to see other alternatives to find. I personally use fd (https://github.com/sharkdp/fd) a lot, as I find the UX much better. There is one thing that I think could be better, around the difference between "wanting to list all files that follow a certain pattern" and "wanting to find one or a few specific files". Technically, those are the same, but an issue I'll often run into is wanting to search something in dotfiles (for example the Go tools), use the unrestricted mode, and it'll find the few files I'm looking for, alongside hundreds of files coming from some cache/backup directory somewhere. This happens even more with rg, as it'll look through the files contents.

I'm not sure if this is me not using the tool how I should, me not using Linux how I should, me using the wrong tool for this job, something missing from the tool or something else entirely. I wonder if other people have this similar "double usage issue", and I'm interested in ways to avoid it.