---
id: 2026-01-31T17:49:00-0500
title: 2026-01-31 17:49:00
tags:
  - authorship/other
  - exclude-from-word-count
  - status/draft
daily: "[[2026-01-31]]"
---
# 2026-01-31 17:49:00

> [!quote] [Linux Bash Shell Script Error: cannot execute: required file not found - Unix Stack Exchange](https://unix.stackexchange.com/questions/721844/linux-bash-shell-script-error-cannot-execute-required-file-not-found)
>
> > [!quote] [ctrl-alt-delor](https://unix.stackexchange.com/users/4778/) 2022-10-21 08:16
> > Note: use of back ticks e.g. `... ``command`` ...` is deprecated. Use the newer easier to use `"$(command)"` (but yes this simple use with echo is hoop jumping). Use of `.sh` at the end of file names is not Unix. And it violates the principle of abstraction, as it leaks implementation detail. Just name them by what they do, not how they do it.
>
> > [!quote] [Kusalananda](https://unix.stackexchange.com/users/116858/) 2022-10-21 08:22
> > @ctrl-alt-delor They are most definitely not deprecated, only awkward to use and should be avoided. In this particular case, any type of command substitution would be inappropriate. As for naming files, that's really up to the user. If you are concerned with abstraction, you could suggest the user uses the `hostname` command directly rather than via a nonsensical script with a function.
>
> > [!quote] ctrl-alt-delor 2022-10-21 08:29
> > `deprecate` : express disapproval of. I disapprove. You say should be avoided. Thus deprecated. As for up to the user. I agree, it is the same for drug use. And the best abstraction is no abstraction (it depends). However I assume the examples were minimum non-working examples.
>
> > [!quote] [Ed Swangren](https://unix.stackexchange.com/users/597584/) 2024-09-28 07:46
> > @ctrl-alt-delor `deprecate(3):` to withdraw official support for or discourage the use of (something, such as a software product) in favor of a newer or better alternative" you're right, but only accidentally, so no credit given and mockery warranted. Citing a dictionary definition in a technical context is always wrong, citing the wrong one is lazy and stupid, and citing your opinion as evidence is in line with what I'd expect after #1 and #2. No one cares.
