Several more states have introduced/passed similar legislation already, so it's becoming more of a problem; or see Brazil's law.

While I know what you mean, you also need the "dummies" to encourage wider use of a platform.

While I like and use Lemmy on mobile, it's really just not the same niche as Reddit, because of the tiny (by comparison) userbase and fractured communities across servers.

If the Fediverse wants to take off as the dominant platform type, then we would need a larger audience willing to engage and popularize the idea... At least for "social" platforms like this.

Or use a while-read loop anyway?

while read -r foo; do
  cmd "${foo}" 
done < <(ls -1)

(But don't script ls)

The find example should just use -exec grep "USB" {} + also, though -exec generally is the correct way to do this.

iptables --> nftables

And if you really want the iptables UX, iptables-nft is also an option (at least on Debian). While I prefer firewalld most of the time on a server, my boss really wants to stick with the same tools he's used for 20yr; so iptables-nft it is.

I've somewhat recently taken TrueNAS to avoid the headache of DKMS for ZFS support.

While it is nice to know I basically don't have to worry about that, the rest of it is pretty painful -- I can't even install a package without manually running it in docker.

We've in a CentOS/Rocky shop at work until recently, moving to Debian.

If I has to redo my NAS, is take Debian or something and call it a day. The hassle of TrueNAS and similar distros do not really seem worth it, if you want more control.

Dunno if you saw, office.com now refers to Office (the "launcher" ?) as:

the Microsoft 365 Copilot App (formerly Office)

Can't wait for Copilot OS (formerly Windows)

I recently had to port a bash script to POSIX because my boss demands we still use at, and wants exec to look like at -f.

99% of my time is spent in bash, so in conjunction with the POSIX spec documentation, Copilot was useful in finding a solution for >(and ...) redirection (logging related), as my bash solution was not compliant.

It was helpful, but I still took the time to locate examples in the spec, and validate every single answer I got.

Outside of this, it has basically never been more productive than doing my own searches, research & testing (sysadmin & "devops").

I've recently switched from np++ to Sublime for some non-standard issues -- I would say that could be closer in performance & extensibility to Vim/Emacs; though limited to GUI and non-FOSS of course.

If we're including shell scripts/functions as "terminal commands":

• bm()
  • Zoxide wasn't quite what I wanted
  • Quick jump to a static list of directories with some alias
• mkcd()
  • Basic mkdir && cd
  • Some extra stuff for my specific workflow
• bashlib
  • My small, but helpful, "stdlib"
• gitclone.sh
  • git clone wrapper without needing to give a full URI
• md2d.sh
  • pandoc wrapper
  • I'm required to provide documentation at work in docx format, so I use this to avoid Office as much as possible

If we just mean terminal applications:

• hyperfine
• jq and yq
  • Honorable mention: xmlstarlet
• shellcheck
  • Primarily used via LSP
  • CLI tool still used when my boss sends me AI Slop scripts I have to fix

A couple of bash specific items I'm using quite often these days:

• mapfile
• printf '%(datefmt)T
  • Annoying %T doesn't expand to true ISO-8601 compliance
• (( expr ))
  • Truly saves my ass every year in Advent of Code, despite the limitations

shell built-in command

After looking into it a bit more, its at least a builtin for bash but is otherwise not POSIX. I guess nohup ... & would be the POSIX compliant equivalent, though still not a builtin.

Its my understanding that & backgrounds, not necessarily detaches, a process -- if the parent process closes, I think the background tasks would still be wait()ed on, if only using &.

There are times when dealing with annoying field separators that awk is a more convenient tool -- though, I'm also now at the stage that I want to do as much with bash-builtins as I possibly can.

You can get rid of those greps, btw:

ps aux | awk '/zoom/ && $0 !~ /awk/ {print $2}'

Or just use pgrep.