Document explaining the development of a bc/dc clone. Might be a good example to follow, if I ever make a public project.

Forth-like, cross-platform language with native code compiler. Runs on
- Microsoft Windows XP/7/8/10
- macOS 10.7 and later (only 64-bit; 32-bit is no longer supported)
- Linux - Ubuntu 14.04 and later, and derivatives or similar systems based on libc6
- Raspbian (Raspberry Pi version of Debian Linux; also works for similar SBC Linux systems)
- Android 4.4 (API level 19, ARM devices) and later
- iOS 9.0 and later
Found via https://pikchr.org/home/doc/trunk/homepage.md

When hacking up Bash scripts, there are often things such as logging or command-line argument parsing that:
- You need every time
- Come with a number of pitfalls you want to avoid
- Keep you from your actual work
Here’s an attempt to bundle those things in a generalized way so that they are reusable as-is in most scripts.

We call it “BASH3 Boilerplate” or b3bp for short.
Found on https://willschenk.com/articles/2019/computer_setup_script/

It was mentioned on a Lisp-related site or mailing list, I do not recall which one.

The paper
https://www.usenix.org/legacy/publications/library/proceedings/sa92/spencer.pdf
sounds like it is worth reading.

Found via https://vlang.io/ → https://github.com/damon-kwok/v-mode → https://github.com/raxod502/straight.el
The programming language playground https://riju.codes/ looks interesting too.

A simple programming language with syntax similar to Go. Found via https://minnie.tuhs.org/pipermail/tuhs/2022-February/025351.html
A bit later in the same thread, the scripting language Wren https://wren.io/ was mentioned.

While this blog article is about a new feature of the Scheme-based Guix Linux package manager, it contans the following interesting observation about erroneous shell settings: "it’s not uncommon for the shell to mess up with the whole environment. Why? Because, contrary to documented practice, it’s quite common for users to define or override environment variables in the startup files of non-login shells, ~/.bashrc for Bash, ~/.zshrc for Zsh. Instead, environment variable definitions should go to the startup file of login shells—~/.bash_profile, ~/.profile, or similar. But let’s face it: it’s a subtle distinction that few of us know or care about."

It's not about technology for its own sake. It's about being able to implement your ideas.