[mwpmaybe]

This is all great, but as someone who logs into dozens of new-to-me systems every week I am unfortunately better served by learning raw systemctl and journalctl commands and training around them instead of a suite of tools and scripts that I'll need to install and configure anew each time. The fzf that ships with Ubuntu 22.04 and 24.04 doesn't even support all the options used here.

And this is why I daily-drive bash, vi, top, and screen, even on my own systems... although I can usually get away with `apt install htop fzf tmux vim-tiny` (or the equivalent) if necessary. And I don't use many shell or git aliases. Woe is me!

[63stack]

There are always some people in the comments that come out of the woodworks to provide a "this is great but tangential reasons why this does not fit one of my use cases" anecdote.

You can use these tricks the blog post is showing on computers you have full control over, to ease your life a bit, while, at the same time, unbelievably, you can keep using the regular commands on systems where this is not available.

Using these scripts does not mean you no longer need to understand "raw" commands, it's a requirement because it builds on top of those.

[mwpmaybe]

> a "this is great but tangential reasons why this does not fit one of my use cases" anecdote

I understand your point, but I suspect I'm not the only sysadmin-type on HN and that this might be a more common (to this particular audience) use-case than your thesis would suggest.

> Using these scripts does not mean you no longer need to understand "raw" commands

Sure, but the reality for many is that if you spend your working hours typing "sstart" and "sj" and "gc" and "ll" and whatever else in zsh with a billion plugins, one day you'll find yourself on a P1 call at 2 AM going:

>> oops, that's not it

>> erg, I guess I made an alias for that on my machine

>> what are the flags for ps again?

>> why did that glob delete the wrong files?

>> why isn't journalctl showing me all the logs??

etc.

Whereas if you have to type e.g. `ps auxfwww` and `journalctl -xel --user` a billion times a day, that will be locked and loaded when you need it. Even if you can't necessarily remember what all the arguments do. ;)

[pram]

My thoughts on it. Also typically you're only going to be restarting so many things ever so the invocation is probably sitting in reverse search (and thus fzf) anyway.