The most interesting answers would be those where the majority of tech workers today would most likely choose a new shiny technology but you still use a boring technology for it. Please do provide some context for your answers. Why did you choose the boring technology? What problems do you solve with it? Why didn't you switch to another popular alternative for it?
Edit - Midnight Commander - Although i did upgrade to the SpeedCommander.
Using a modern word processor definitely allows for better revision / saving / duplication, but most writings shouldn't require so much thought / preparation. Not having a display to distract while thinking definitely allows the author to focus.
* C, because it is so easy to implement anything you can imagine, there are libraries for everything, and the resulting code runs very fast (although I deliberately limit myself to safe constructs only).
* C++, because many things are so much easier (and often safer) to do in C++ than in C, and again you have libraries for everything, and the code runs fast. Modern C++ is quite nice. And you don't have to know all of C++ to write reasonably efficient code.
* Python, because there is nothing faster when you need to prepare a prototype, and sometimes the prototype is good enough, especially in io-bound code.
* PHP, because you can quickly code practically any web solution extremely quickly (and integrate with any JS framework you like), and the deployment is a breeze. Again, modern PHP has very little in common with the old language you may remember from 2000.
* Bash and traditional Unix tools as they allow me to do my job in no time. I took time to learn what each one is for and it just saves time. Yes, I could use Python to grab the first fields from a CSV file but normally I'll do it faster with AWK etc.
That said, I love experimenting with new languages like Nim, they are a breath of fresh air and quite fun to tinker with. Nevertheless, in my day to day work, I find myself using proven tools most often.
I tried many apps ought to replace pen and paper, but it never clicked.
Oh, wait? Those are not 'boring technologies', they're just 'old technologies' - nothing boring about them.
Computer-related 'boring' technologies in daily use: the nix tool set - shell, awk, sed, perl, curl and the like plus some relatively newcomers like jq and xidel to handle web-related things. Vim in one of its guises. Instead of fighting npm and the myriad of ever-changing related tools to provide CLI tools I tend to use the former to open up APIs to those who live on the command line. All the claims of shell being unsuitable for such projects notwithstanding these tools tend to work reliably while being self-contained - a single file pulling in a single config file and sometimes a common functions file. No transpilers needed, no packers, no shitload of libraries, no nuthin' - just a few hundred lines of 'boring' shell like e.g. this BookStack* API CLI [1] I made a week and a bit ago.
Storage: MDADM and LVM hosting ext4 instead of ZFS because I like the separation of tasks and the greater flexibility over the latter.
Web: PHP because it works and performs well enough. Java when needed, also because it works and performs well enough. Pure Javascript instead of the jumble of libraries/frameworks/new-ways-of-doing-things because those all too often end up being old-unmaintained-ways-of-doing-things.
System: C over C++/Rust/Zig over Go/Nim/Crystal because it is the Lingua Franca which has stood the test of time and will probably outlive most of those mentioned languages.
Communications: SMTP/IMAP + XMPP and when needed Telegram over Slack/Teams/whatever.
Cloud? Only when I have the hardware under my own control and within reach. The server lives under the stairs, the backup server under some other stairs in another building.
Wired Ethernet over WiFi when possible.
Older hardware, usually rescued from a dumpster or something similar.
The ext4 filesystem. Yes, there is no bitrot protection and no snapshots etc, but it's rock-solid as a main OS partition.
IMAP
Bittorrent
I lost my mojo for brand new technologies and frameworks and languages, and I can't ignore the amount of energy and resources that new shiny tech requires, so I stick to low-tech, proven stuff that has been there for eons and will be there for eons, as much as I can.
Cash instead of banks (cryptocurrency is an exception).
Email + forums + IRC (sometimes) instead of Telegram or similar.
Arc lamps instead of LED if it is possible.
Singlespeed bicycle instead of ones with gears.
3-way stereo with paper diffusors and class-A amplifier instead of wide-band 1-way with plastic diffusor and class-D amplifier. And listening to as old records as possible to find on torrents, not on streaming services.
Hardly to say why I chose all of this instead of all of that, I just like it and do not care about someone's laughers.
Anyway I really like it when I want to something more complex than what bash can handle easily.
From software Irfanview for personal use.
- Prey project - device lost and found
- Neovim
- sysstat (sar)
- surfraw
- parallel
- gawk
- gpg for ssh
- VMware ESXi
- hwrng for entropy
- Colo your own servers
- /etc/securetty + PAM for passwordless root login on the actual console
- Kerb 5, LDAP, RADIUS
- SNMP
- Nagios-compatible collectors
grep/ag - text search instead of a big name startup. vim - for text editing. zsh/tmux - for terminal stuff.
Google Keep (replace with text files) - for TODO and not some fancy task management software.