Earlier quoted context omitted.
I do it at least for ripgrep.
Fzf has saved me so much time over the years. It's so good.
Yes, good point. I use it all the time too. Plus fzf-lua in neovim which depends on it.
Modern Linux tools
161–170 of 219 posts
Re: Modern Linux tools
#162These may be objectively superior (I haven't tested), but I have come to realize (like so many others) that if you ever change your OS installation, set up VMs, or SSH anywhere, preferring these is just an uphill battle that never ends. I don't want to have to set these up in every new environment I operate in, or even use a mix of these on my personal computer and the traditional ones elsewhere. Learn the classic to…
How hard is it to set up your tooling?
I have a chef cookbook that sets up all the tools I like to have on my VMs. When I bootstrap a VM it includes all the stuff I want like fish shell and other things that aren’t standard. The chef cookbook also manages my SSH keys and settings.
Re: Modern Linux tools
#163Every time such a list is posted, it tends to generate a lot of debate, but I do think there is at least 2 tools that are really a good addition to any terminal : `fd`: first I find that the argument semantic is way better than `find`, but that is more a bonus than a real killer feature. Now, it being much, much faster than `find` on most setup, I would consider a valuable feature. But the killer feature for me is th…
Great tools like dasel are format agnostic on input and output.
Re: Modern Linux tools
#164qq should be on this list. It's like jq but works with multiple file formats, including JSON, YAML, XML, &c. and has a really cool interactive TUI mode. https://github.com/JFryy/qq
Did you try https://github.com/TomWright/dasel ?
Re: Modern Linux tools
#165Earlier quoted context omitted.
> that if you ever change your OS installation apt-get/pacman/dnf/brew install You'll need install those and other tools (your favorite browser, you favorite text editor, etc) anyway if you're changing your OS. > or SSH anywhere When you connect through SSH you don't have GUI and that's not a reason for avoiding using GUI tools, for example. > even use a mix of these on my personal computer and the traditional ones e…
> You'll need install those and other tools (your favorite browser, you favorite text editor, etc) anyway if you're changing your OS. The point is that sometimes you're SSHing to a lightweight headless server or something and you can't (or can't easily) install software.
It does seem like a lot of these tools basically have the same “muscle memory” options anyway.
Re: Modern Linux tools
#166Earlier quoted context omitted.
That is what the post you responding to is saying
I’m still responding to the first sentence. It’s not a differentiator, even to smart engineers who understand the programming language in question (e.g., Go or Rust). Whenever an engineer leads with the programming language, I know that it’s just their favorite. You can write great Python, Ruby, Go or Rust, or you can write crappy Python, Ruby, Go, or Rust. Yes, some languages make more sense for certain environments…
> You can write great Python, Ruby, Go or Rust, or you can write crappy Python, Ruby, Go, or Rust. ... the programming language is never the differentiator itself
This is called "the fallacy of grey". Very common.
https://www.lesswrong.com/posts/dLJv2CoRCgeC2mPgj/the-fallac...
Re: Modern Linux tools
#167Earlier quoted context omitted.
> that if you ever change your OS installation apt-get/pacman/dnf/brew install You'll need install those and other tools (your favorite browser, you favorite text editor, etc) anyway if you're changing your OS. > or SSH anywhere When you connect through SSH you don't have GUI and that's not a reason for avoiding using GUI tools, for example. > even use a mix of these on my personal computer and the traditional ones e…
> apt-get/pacman/dnf/brew install If only it were so simple. Not every tool comes from a package with the same name, (delta is git-delta, "z" is zoxide, which I'm not sure I'd remember off the top of my head when installing on a new system). On top of that, you might not like the defaults of every tool, so you'll have config files that you need to copy over or recreate (and hopefully sync between the computers where…
After installing it, git clone and then stow .
Re: Modern Linux tools
#168Earlier quoted context omitted.
I know well enough my way around vi, because although XEmacs was my editor during the 1990's when working on UNIX systems, when visiting customers there was a very high probability that they only had ed and vi installed on their server systems. Many folks nowadays don't get how lucky they are, not having to do UNIX development on a time-sharing system, although cloud systems kind of replicate the experience.
Ed is the standard text editor.
Doing edlin as high-school typing exam was already enough, and ed wasn't much better, which was an opinion shared by our customers back then.
Re: Modern Linux tools
#169Earlier quoted context omitted.
I find the opposite to be true. Most of these are really just reinventing the wheel of foundational GNU tools that are really powerful provided one has spent some time on them.
It's like people dont even know why people use or want these "modern" tools. It's called "sane defaults", and improved UX. Those "foundational GNU tools" just suck, sure, people are familiar with them and they are everywhere, but they just plain suck. For many common operations you'd want to do by default with grep/find and so on, you have to type mountains of random gibberish to get it done. And that random gibberis…
Sounds like a skill issue.
Re: Modern Linux tools
#170Earlier quoted context omitted.
> that if you ever change your OS installation apt-get/pacman/dnf/brew install You'll need install those and other tools (your favorite browser, you favorite text editor, etc) anyway if you're changing your OS. > or SSH anywhere When you connect through SSH you don't have GUI and that's not a reason for avoiding using GUI tools, for example. > even use a mix of these on my personal computer and the traditional ones e…
> apt-get/pacman/dnf/brew install If only it were so simple. Not every tool comes from a package with the same name, (delta is git-delta, "z" is zoxide, which I'm not sure I'd remember off the top of my head when installing on a new system). On top of that, you might not like the defaults of every tool, so you'll have config files that you need to copy over or recreate (and hopefully sync between the computers where…
Chezmoi makes this really easy: https://www.chezmoi.io/