Well, that won’t work on openbsd (and probably freebsd), because non-default.stuff lands in /usr/local/bin.

For Linux you should be fine though.

Uhm, yes. I noted exactly that as well.

Also bash is not always at /bin/bash :-)

Let me just drop my materials for a talk i’ve given about basically this topic: https://codeberg.org/flart/you_suck_at_shell_scripting/src/branch/main/you_suck.md

Mainly because: The linked article is all nice and dandy, but it completely ignores the topic of double brackets and why they’re nice.

And also, and this is my very strong opinion: if you end up thinking about exception handling (like the mentioned traps) in shell scripts, you should stop immediately and switch to a proper programming language.

Shell scripts are great, i love them. But they have an area they’re good for and a lot of areas where they aren’t.

Oh it will definitely tell you something. It will be complete bullshit, but it’s something.

Of course not. But the shareholder value!

Because of Windows.

They also apparently didn’t do any input validation. This is why a faulty config was able to even trigger all of that.

Some nice ideas in there.

Only the “markdownquote” thing is kinda pointless, especially since they mention it’s mainly used in vim. Because vim can do exactly that already without the need of an external script. Do ctrl+v, mark the lines you want, press “I” (capital i), insert the desired thing, press esc and voila… all the selected lines are now prepended with the desired thing.

edited to make my comment sound less harsh: Nothing wrong with building your own solution if that feels better to oneself though :-)

Ousterhouts book was very much an eye opener for me when i stumbled over it some years ago.

All those recommendations from the “clean code” corner always felt a tad off to me, but i couldn’t put the finger on it. Then i read this small and nicely written book an suddenly the fog cleared up.

Is that a triptopus?

Oh wow, people like that really do exist.

Oh wow.

That looks like an overly complicated solution to a problem that doesn’t exist. Synching stuff that is in git? Why not just use… git? Also npm… and the example has an env var named “DB_PASS” in it. You never put passwords in version control.

A philosophy of software design, by John Ousterhout.

Short book with some fresh approaches that i like way more than some of the established ones.

I kinda get that people somehow like the overall idea of this approach.

But who is, excuse my french, fucking maintain that crap in the long run?

Wow, you even caught the pike with that one, over on Mastodon.

<3

How does that even relate?

Mail encryption has nothing to do with how the mail is formatted (html vs plain text). And the client protocol for fetching the mail from the server also has nothing to do with that.

Well, who said the c in c/something is NOT commune? ;-)