Depending on the details of your setup and precisely why you're attempting this, I would also recommend Avahi/Zeroconf (lets you type "$HOSTNAME.local" or simply populate some favorites/bookmarks on the client machines (typing the bookmark name will generally autocomplete).
I sure wish more of these electric trucks came with paint-free body panels. Say what you will about the Cybertruck, but the idea of a truck that doesn't have paint is very attractive to me. Seems like this one is moving away from plastic to steel, and I haven't seen what the Slate so I imagine it's probably painted steel as well. Plastic, stainless, whatever...I just don't want a paint job to worry about.
Just to maybe save someone a couple of seconds of time: the '-W interactive' bit is a mawk-specific option (-W is for implementation-specific options). Not 100% certain but it looks like the gawk default does something similar so no additional option is needed, I think.
Thomas, every time I read something you write it's a delight. I love your writing style, and it reads to me like you're always putting effort into making it succinct yet unambiguous, without unnecessary embellishment.
Just so you know: this app does not support zooming, it only switches between lenses. (This was a little surprising to me, but I'm not a video professional.)
As you learn to understand people better, life becomes vastly easier. Have you ever misread a social situation? Accidentally hurt someone? Not realize what the person you're negotiating with really wants? All these things become easier as you get better at listening, emphasizing, and understanding.
I have the box set of some of your other zines, so I instantly bought two copies (as I did with the box set). One is for my twelve year old daughter who's been fascinated by your stuff for years, and one to take to work, where it will constantly be lent out to other people.
Love your work. Always fascinates me to see how people approach simplifying something complicated. These remind me of a feeling I also get when I'm reading Scott McCloud: comics are vastly underrated for educational content.
As a software developer, I have long-since ingrained the behavior of looking up the documentation before I assume something works in a particular way. Perhaps doubly so when shell scripting, where I have to verify if I can rely on a particular package being present, or the minimum version of something I can expect, or what the output is guaranteed to be.
When I was considering using fgrep, I looked it up; lo and behold, it's not part of the POSIX standard. So I used the option instead, and have since.
I'm a little puzzled why people have problems with these little things when it feels like it's pretty common for tools to change given enough time (for example, ifconfig and netstat to ip and ss). It's just essentially an API that gradually refines over time.
It's not that common for tools that have been around for decades, and don't have system dependencies (like your network configuration examples do) to change.
egrep and fgrep are used on ad hoc command lines daily, and option alternatives are less convenient to use. I personally use 'egrep -o' and 'fgrep -f <(...)' all the time. I already find it tedious to have to type 'sed -r' and am half-considering wrapping it in an 'esed' variant.
Eliminating egrep and fgrep is change for the sake of change. Removing a couple of hard links from a few bin directories would be the total positive achievement, at the cost of years of work removing the utilities from scripts - or more likely, adding the links back, or variants thereof, like shell scripts which add -E / -F as required.
Step one is to be aware of your capacity to hurt; it seems like you have this covered. I find that over time my awareness has grown, which has caused me to care more (and be more careful) about the feelings of who I am communicating with.
I used to think something like, "If I can just get them to see that I didn't mean to hurt/mean it that way, they clearly won't be hurt!" This is not at all true for many (most?), and like many matters of emotion that's ok. I was not originally aware of the phrase "intent is not impact" but this idea is what I'm trying to describe above.
It is very important to approach this from a place of humility and non-defensiveness. Be eager to apologize for the hurt you caused. I'm sure you're a great person who doesn't wish to hurt people; apologizing doesn't mean that you're sorry you tried to hurt them but that you're sorry that you did. Think of it as the equivalent of apologizing for accidentally elbowing someone in the head. It's not like you meant to, but their head still hurts where you elbowed it.
Actually caring helps a lot; it helps remind you to think before you speak or write, and to pay attention to reactions. If you care, you tend to get better over time.
