this post was submitted on 30 Oct 2023
120 points (100.0% liked)
Linux
1259 readers
82 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I have a strong bias for staying with tools that are installed by default. After this many years working with new systems of my own, containers, and systems where I'm not root, the added value of an alternativehas to be quite high for me to switch a core utility.
Thay said, I've found fd, ripgrep, and helix to meet that criteria. The others, not so much; they either don't improve upon or add functionality that's not available, or simply add eye candy. Gaining pretty colors is nice, but not worth losing familiarity with ubiquitous tools.
git-delta is an exception where the syntax highlighting can make a functional difference in code diffs. Not so much that I think about installing it, or using it outside of indirect VCS configuration, but it is a good example of using style for more than just eye candy. I prefer difftastic, but they do much the same.
While it's not a replacement for an existing tool and isn't in your list, nnn is very helpful in many cases, especially bulk renames and reorganizations.
The thing I like about a lot of these is that I don't lose familiarity with existing tools. When I end up on a cluster that doesn't have them, I'm a bit annoyed, but I can still operate just fine.
The principle exception to this is actually
fd- I now findfind(har!) almost unusable without having a man page open in a separate terminal. But that's becausefdis so much more ergonomic and powerful, I would never give it up unless forced.I unfortunately do not have your crystaline perfect recall. I used vi/m for nearly 20 years before drifting onto kakoune and now helix; I've been using them for about a year, and it's getting harder and harder to not make reflexive mistakes when I'm trying to use vim. sed was already odd with regex escaping (parens but not brackets? Why??), and I know the less I use it the more I'll forget. This is crippling when I have to work on a system that doesn't have these new tools installed.
What I mean is that many of them have basically the same functionality with the same arguments. I don't mean I have pristine memory for the differences, but things like
alias ls="eza"is basically a drop in replacement with some added features. So when I'm on a server without it, everything is basically the same, just less fancy.Helix and fd are an example of the other pattern - they are huge improvements over existing tools, to the point that when I'm forced to use the basic ones, I'm actively crippled. But as an argument not to use the better tool day-to-day, this doesn't make sense to me. Why would I force myself to suffer 95% of the time to save myself from suffering 5% of the time?
I mean, for helix/vi it's even clearer. Vanilla vi is basically unusable for me anyway, and I needed a huge number of plugins to be serviceable - on a basic cluster environment, I'm going to be crippled anyway, so...
Can you give an example on the reorganization benefits with nnn? I am using it myself but I still feel like a noob with it.
So, I did a whole asciinema demonstration to show you, but it was getting tedious. It started to turn into a whole tutorial, and I really didn't want to go there. That's why it's taken so long for me to reply.
But there are three things I do with nnn:
I don't "live" in nnn; it's a tool I open when I want to do certain things - it's fast enough to use this way. But you certainly could, since nnn can fork shell processes in selected directories.
The last point is new to me, will check it out, thank you!