Hacker News new | ask | show | jobs
by wereallterrrist 1243 days ago
Every single tool that Ive replaced with a rust-replacement is faster, more stabld, has healthier development and release cycles.

Uutils, helix, zellij, ripgrep, and countless others.

Ive stopped caring (mostly) to convince others of it, but many, many Rust projects are clearly started by very experienced folks that know how to release and foster a community.
2 comments
spoiler 1243 days ago
I think most of this stems from the fact you can focus on the problem you want to solve, instead of mundane plumbing (like in C or C++ project).

Suuuure, some people will complain about the borrow checker, but I think it's people who are mostly inexperienced with Rust. It's not really an issue for anyone after they've played with the language for a while.

Like, these days I rarely have to debug a borrowing errors, and if I do it's a few minutes of work tops.

link
wereallterrrist 1242 days ago
more examples that I thought of while writing this; `fd` and `sd` which I use daily now. and since my nix config lists my rust tools, because I'm a `mut hardcoreZealot` TM: `exa` (try `exa -al --tree --level 2`), `dua` (try `du -x i`), `gitui`, `jless`, `bat` (sparingly)

`xplr` and `joshuto` are clearly thought-out non-trivial TUI file explorers that seem to scale to the naive and a certain power-user type.

`difftastic` is a very cool replacement `diff`.

`jj` is compatible with git, and like git-branchless, but I'll bet on `jj` for a number of reasons. It's also awesome and in 3 years there's going to be some amazing tools built with `jj` and...

(not a daily/semi-daily use, at all, but special mention:) `git-oxide`, I mean, you can guess from the name, the monthly reports show just how incredibly thoughtful the author is and just how incredibly viable and already-usable this project is (especially given the complexity which I really would not have understood without the thorough monthly updates).

followup, there's no reason for this to really mean anything, or for anyone to "believe" me, but I just opened this post on reddit:

https://old.reddit.com/r/zfs/comments/10pdspe/take_your_zfsb...

and wow, what a smart tool, and a smart way to release it. I know how to mount a snapshot, and ripgrep/fd through it, could script that, but making that resilient would suck. The way this is presented is smart. It's a new OSS project, shows example usage in the reddit post. Anyway, I thought of my comment earlier, and of course, there it is, `Cargo.lock`, bias confirmed. And a tagged release. And has a `LICENSE`. And has committed `Cargo.lock`.

For the sake of not replying too much I'll say I'd echo everything spoiler wrote in this posts' sibling comment. And at the risk of coming across poorly, there's something that's a cross of stockholm-syndrome and sunk cost fallacy and it seems like when certain potentially displacing technologies gain more and more steam, there's a louder and louder minority that claim that this new paradigm is just too disruptive and what are they teaching our kids. (oops)

link