16
better tools thread
(awful.systems)
submitted
1 year ago* (last edited 1 year ago)
by
froztbyte@awful.systems
to
c/notawfultech@awful.systems
this is in part because it's for (yet another) post I'm working on, but I figured I'd pop some things here and see if others have contributions too. the post will be completed (and include examples, usecases, etc), but, yeah.
I've always taken a fairly strong interest in the tooling I use, for QoL and dtrt reasons usually (but also sometimes tool capability). conversely, I also have things I absolutely loathe using
- wireguard. a far better vpn software and protocol than most others (and I have slung tunnels with many a vpn protocol). been using this a few years already, even before the ios app beta came around. good shit, take a look if you haven't before
- smallstep cli. it's one of two pieces of Go software I actually like. smallstep is trying to build its own ecosystem of CA tools and solutions (and that's usable in its own right, albeit by default focused to containershit), but the cli is great for what you typically want with certificate handling. compare
step certificate inspect file
andstep certificate inspect --insecure https://totallyreal.froztbyte.net/
to the bullshit you need with openssl. check it out - restic. the other of the two Go-softwares I like. I posted about it here previously
- rust cli things! oh damn there's so many, I'm going to put them on their own list below
- zsh, extremely lazily configured, with my own little module and scoping system and no oh-my-zsh. fish has been a thing I've seen people be happy about but I'm just an extremely lazy computerer so zsh it stays. zsh's complexity is extremely nonzero and it definitely has sharp edges, but it does work well. sunk cost, I guess. bonus round: race your zsh, check your times:
% hyperfine -m 50 'zsh -i -c echo'
Benchmark 1: zsh -i -c echo
Time (mean ± σ): 69.1 ms ± 2.8 ms [User: 35.1 ms, System: 28.6 ms]
Range (min … max): 67.0 ms … 86.2 ms 50 runs
- magic-wormhole. this is a really, really neat little bit of software for just fucking sending files to someone.
wormhole send filename
one side,wormhole receive the-code-it-gives
the other side, bam! it uses SPAKE2 (disclaimer: I did help review that post, it's still good) for session-tied keying, and it's just generally good software - [macos specifically] alfred. I gotta say, I barely use this to its full potential, and even so it is a great bit of assistive stuff. more capable than spotlight, has a variety of extensibility, and generally snappy as hell.
- [macos specifically] choosy. I use this to control link-routing and link-opening on my workstation to a fairly wide degree (because a lot of other software irks me, and does the wrong thing by default). this will be a fuller post on its own, too
- [macos specifically] little snitch. application-level per-connection highly granular-capable firewalling. with profiles. their site does a decent explanation of it. the first few days of setup tends to be Quite Involved with how many rules you need to add (and you'll probably be surprised at just how many things try to make various kinds of metrics etc connections), but well worth it. one of the ways to make modern software less intolerable. (honorary extra mention: obdev makes a number of handy pieces of mac software, check their site out)
- [macos specifically] soundsource. highly capable per-application per-sink audio control software. with the ability to pop in VSTs and AUs at multiple points. extremely helpful for a lot of things (such as perma-muting discord, which never shuts up, even in system dnd mode)
rust tools:
- b3sum. file checksum thing, but using blake3. fast!. worth checking out. probably still niche, might catch on eventually
- hyperfine. does what it says on the tin. see example use above.
- dust. like
du
, but better, and way faster. oh dear god it is so much faster. I deal with a lot of pets, and this thing is one of the invaluables in dealing with those. - ripgrep. the one on this list that people are most likely to know. grep, but better, and faster.
- fd. again, find but better and faster.
- tokei. sloccount but not shit. handy for if you quickly want to assess a codebase/repo.
- bottom. down the evolutionary chain from
top
andhtop
, has more feature modes and a number of neat interactive view functions/helpers
honorary mentions (things I know of but don't use that much):
- mrh. not doing as much consulting as I used to, using it less. quickly checks all git(?) repos in a path for uncommitted changes
- fzf. still haven't really gotten to integrating it into my usage
- just. need to get to using it more.
- jql. I ... tend to avoid jq? my "this should be in a program. with safety rails." reflex often kicks in when I see jq things. haven't really explored this
- rtx. their tagline is "a better asdf". I like the idea of it because asdf is a miserable little pile of shell scripts and fuck that, but I still haven't really gotten to using it in anger myself. I have my own wrapper methods for keeping pyenv/nvm/etc out of my shell unless needed
- pomsky. previously
rulex
. regex creation tool and language. been using it a little bit. not enough to comment in detail yet
I really need to get to trying out doom sometime. still on spacemacs, and yeah fuck it is slow. I don't have the desire to write my own emacs config from scratch either.
parallel: yeah. I.... it's mostly sorta good? but god I hate it. the way the args layout works sucks. I've looked for alternatives and haven't really found any. I'll often still just go for
xargs -P -n 1
over parallel because parallel just ughdoom’s compilation model is great! it AOC native compiles everything it can, then the JIT runs for everything else. it’s all pinned to specific versions of packages too so breakages are relatively rare. there’s even a package I use that replaces doom’s build mechanism with Nix, though it’s in desperate need of updates for newer versions of doom
I agree on parallel, it’s a good tool to have but I do wish there was a good alternative. parallelizing tasks like it does feels like something that should maybe be built into my shell, especially given how good desktops are at multiprocess workloads now — even something like a multiprocess
for
loop that operates sensibly could be a massive improvement over anything we have nowevery so often I find myself wanting the ability to run a pipe chain but with some kind of resumability, in a just-far-enough-to-be-beyond-job-control sense that still isn't enough to write a whole-ass program
and the amount of times I write the pattern
while read line; do ...{nested instructions, multiple shellscripts}...; done < inputfile
, samebut I know that doing this on current shells would be a big ball of spaghetti nightmarecode, and be incredibly painful to debug when it any time fails (and it is a when, not an if, because current shells just don't have that kind of safety)
continuing down that ideological avenue, I find myself considering that powershell, while being an extremely shitty shell, really does have a nice thing going with the rich API surface (and that follows from other things in the environment, but I digress)
that leads me to thinking about things like oilshell etc, which while interesting still don't really scratch my itches here
at this point about 5~10min has passed since I started writing the pipechain. I breathe deeply, sigh about computers, bang out a shitty one-liner, and wish I had a pile of free money to spend on just building better tools. with a secondary flash of thinking that, despite Developer Experience things being en vogue over in the bay, this just absolutely wouldn't get money because it isn't pretty and visible (and then sigh deeply at that too, bottling up the impending flash of rage)
this also reminds me:
moreutils
byjoeyh
has a bunch of sane handy things, which also include a nicer baselineparallel
. I keep forgetting about that.