Ariel Millennium Thornton @arielmt@computerfairi.es

While not perfect, growing your own tiny server farm can be rewarding.

If the answer you get to a software or coding problem is any variation of "just throw more computing power at it," including using "the cloud" (someone else's computers) instead of your own tiny server farm, the odds are pretty good you're either asking the wrong question or listening to a techbro.

TIL the `which` command is one of those commands everyone (including me) thinks is standard simply because it's everywhere in the Unix & unixlike worlds, but which really isn't, & is nowhere in POSIX.

LWN, "Debian's which hunt," 2021-10-28: https://lwn.net/Articles/874049/

TIL the POSIX-conformant "which" is `command -v`: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/command.html

Both image sources lack image descriptions. Description added here.
Web source: https://www.goodtechthings.com/pile-of-complexity/
Twitter source: https://twitter.com/forrestbrazeal/status/1628057409452122112
Did someone say "AIOps"?

Even if I did trust you as much as I trust my OS package manager, I can't trust that it will always be the real you on the other end of my link to you, and it's possible for an attacker to trick curl into giving one script to less and another script to bash. https://web.archive.org/web/20240228190305/https://www.idontplaydarts.com/2016/04/detecting-curl-pipe-bash-server-side/ Why set yourself up as a huge target like this?

With all the talk recently about making various forms of code safety national priorities, why in the world does any major compiler promoting built-in code safety features still think the official way to install it should be the anything but safe code delivery method curl-pipe-shell?