cargo-binstall
fd
cargo-binstall | fd | |
---|---|---|
24 | 172 | |
1,304 | 31,668 | |
4.8% | - | |
9.5 | 8.8 | |
about 22 hours ago | 4 days ago | |
Rust | Rust | |
GNU General Public License v3.0 only | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
cargo-binstall
-
Cargo Binstall 1.0.0 release
Unfortunately not really usable in production (for me) until https://github.com/cargo-bins/cargo-binstall/issues/1 is fixed :( Really much looking forward to it though, as I think it's a great addition to the Rust ecosystem!
-
Oxidise your Infrastructure using Shuttle.rs
Oh looks like cargo-binstall is currently broken (https://github.com/cargo-bins/cargo-binstall/issues/1094)
-
Ludusavi can now back up your game saves to the cloud and detect Lutris saves
Unfortunately, I ended up running into an issue with the zip support, but I'll come back to it once this is fixed: https://github.com/cargo-bins/cargo-binstall/issues/1080
-
Strange lifetime error: Requires to be `'static`
I've encountered a strange lifetime error when developing new features in cargo-binstall:
-
AMDGPU_TOP - tool to show AMDGPU usage
Once you feel like releasing it, could you please add binstall support?
-
[rcargo] quick tool for faster crate building on remote workstations
I think in a similar vein there is cargo-binstall that is a cargo install alternative that attempts to use pre-built binary artifacts when possible
-
Faster Apple Builds with the lld Linker
I hope ld64 and lld add supports for plugin-opt I'm trying to enable cross-lang-lto on MacOS but failed due to -plugin-opt not supported.
-
Install a CLI in a project (not globally)
You can use cargo-binstall --install-path to install binaries to custom locations.
-
Release engineering is exhausting so here's cargo-dist
If you happen to install a lot of things with cargo, check out cargo-binstall: https://github.com/cargo-bins/cargo-binstall
It'll fetch the binary release from the repo so you don't have to compile it yourself.
-
Thoughts about updating a rust cli via a sub command for improved dev experience
I'd recommend to use cargo-binstall, which can download pre-built artifacts from github release.
fd
-
Level Up Your Dev Workflow: Conquer Web Development with a Blazing Fast Neovim Setup (Part 1)
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: A command-line benchmarking tool
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
-
Z – Jump Around
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
-
Unix as IDE: Introduction (2012)
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
- Tell HN: My Favorite Tools
-
Potencializando Sua Experiência no Linux: Conheça as Ferramentas em Rust para um Desenvolvimento Eficiente
Descubra mais sobre o fd em: https://github.com/sharkdp/fd
-
Making Hard Things Easy
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:
-
🐚🦀Comandos shell reescritos em Rust
fd
-
Oils 0.17.0 – YSH Is Becoming Real
> 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
-
Bfs 3.0: The Fastest Find Yet
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.
What are some alternatives?
pwninit - pwninit - automate starting binary exploit challenges
telescope.nvim - Find, Filter, Preview, Pick. All lua, all the time.
cargo-quickinstall - pre-compiled binary packages for `cargo install` [Moved to: https://github.com/cargo-bins/cargo-quickinstall]
ripgrep - ripgrep recursively searches directories for a regex pattern while respecting your gitignore
ez_term - Terminal UI framework based on templates and focused on simplicity.
fzf - :cherry_blossom: A command-line fuzzy finder
nue - I/O and binary data encoding for Rust
exa - A modern replacement for ‘ls’.
docker-cargo-binstall
skim - Fuzzy Finder in rust!
amdgpu_top - Tool to display AMDGPU usage
vim-grepper - :space_invader: Helps you win at grep.