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.
AFAIR MC is for Unices only, whereas SC is for Windows. Out of curiosity: why did you decide to use a commercial product when open alternatives are available, such as FAR?
FAR is new to me though - I'll check it out though ! Thanks, might be my new favorite after all !
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.
I experience a similar kind of perfectionist-anxiety-induced procrastination when I write, and it’s always bothered me that none of the “distraction-free” writing apps (I use Ulysses) that come with typewriter modes[1] don’t have an option to disable backspace or even re-map it to strikethrough.
I'd actually enjoy having a typewriter and being locked somewhere far and not have to think about build times. I remember an interview with a hacker who wrote code on paper while he was in jail, said it was extremely productive for him. A lot of modern writers also use typewriters so they can focus better without internet access.
* 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.
- ZFS is not in the Linux kernel so I don't want to use it for a daily work machine
- btrfs works fine but its tools to undelete/recover files when something did go wrong are pretty bad
- XFS looks ancient, not sure how good it is
- ext4 is also pretty aged by now, but is what I use now after my attempt at btrfs. It doesn't have any bitrot protection though
Is there anything else viable today? The above are basically the same choices as I also had 10 years ago
I certainly wouldn't use btrfs. It ate my data at one point, and misbehaves without any provocation. I don't trust it, and am quite vocal about that whenever it's mentioned.
The zfs license is incompatible with gpl.
That being said zfs is awesome, it is simple to use, about as bulletproof you can get.
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.
I always see some really clever usages still popping up!
p2p is indeed exploding, but it's a field that is plagued with money-grabbing schemes and so many pipe dreams only a professional plumber can conceive them. Bittorrent (and its extensions!) has stood the test of time as a protocol that does what it says on the tin and doesn't need "improvements"
As far as i can remember, any email client i ever set up with outlook/gmail/gsuite eventually is set up using IMAP
Moreover, more and more uses of email go through the web and IMAP is an afterthought. Tutanota can send end-to-end encrypted emails... if both parties access emails through the web interface. Or it's a link to an encrypted message, but then you have to send the secure link/password some other way. ProtonMail does the same, if you want IMAP access you need to install an additional software on your machine.
IMAP used to be everywhere, but because people like shiny things it is slowly seen as a bad thing we should get rid of
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.
What's the advantage of Arc lamps over LED?
Sodium lamps gives superior amount of lumens per watts, they are perfect for lighting up my backyard especially if using at least 600W of singular lamp. I miss the times when cities were lighted by sodium, a blue-light pollution is one of the main reason of why I use to hate cities nowadays.
Also I use a cold-cathode fluorescent lamps in some places, they are almost as good as MHL and if used correctly (no often switch on/switch off) I need to replace them maybe once per 10 years. They are hardly to get nowadays, but I have enough of spare ones for all of my expected lifetime.
Both Waterhouse and Ghnxh are encased in planklike wrappings of genuine Qwghlm wool, and the latter carries THE GALVANICK LUCIPHER. The Galvanick Lucipher is of antique design. Ghnxh, who is about a hundred years old, can only smile in condescension at Waterhouse's U.S. Navy flashlight. In the sotto voce tones one might use to correct an enormous social gaffe, he explains that the galvanick lucipher is of such a superior design as to make any further reference to the Navy model a grating embarrassment for everyone concerned. He leads Waterhouse back to a special room behind the room behind the room behind the room behind the pantry, a room that exists solely for maintenance of the galvanick lucipher and the storage of its parts and supplies. The heart of the device is a hand-blown spherical glass jar comparable in volume to a gallon jug. Ghnxh, who suffers from a pretty advanced case of either hypothermia or Parkinson's, maneuvers a glass funnel into the neck of the jar. Then he wrestles a glass carboy from a shelf. The carboy, labeled AQUA REGIA, is filled with a fulminant orange liquid. He removes its glass stopper, hugs it, and heaves it over so that the orange fluid begins to glug out into the funnel and thence into the jar. Where it splashes out onto the tabletop, something very much like smoke curls up as it eats holes just like the thousands of other holes already there. The fumes get into Waterhouse's lungs; they are astoundingly corrosive. He staggers out of the room for a while.
When he ventures back, he finds Ghnxh whittling an electrode from an ingot of pure carbon. The jar of aqua regia has been capped off now, and a variety of anodes, cathodes, and other working substances are suspended in it, held in place by clamps of hammered gold. Thick wires, in insulating sheathes of hand-knit asbestos, twist out of the jar and into the business end of the galvanick lucipher: a copper salad bowl whose mouth is closed off by a Fresnel lens like the ones on a lighthouse. When Ghnxh gets his carbon whittled to just the right size and shape, he fits it into a little hatch in the side of this bowl, and casually throws a Frankensteinian blade switch. A spark pops across the contacts like a firecracker.
For a moment, Waterhouse thinks that one wall of the building has collapsed, exposing them to the direct light of the sun. But Ghnxh has simply turned on the galvanick lucipher, which soon becomes about ten times brighter, as Ghnxh adjusts a bronze thumbscrew. Crushed with shame, Waterhouse puts his Navy flashlight back into its prissy little belt holster, and precedes Ghnxh out of the room, the galvanick lucipher casting palpable warmth on the back of his neck. "We've got about two hours before she goes dead on us," Ghnxh says significantly.
The Cryptonomicon
Neal Stephenson
pp 289-290
And do not confuse an arc lamp with fictional light sources, despite of the starting arc light is really doing that kind of impression you have described.
Meanwhile every single wifi or Bluetooth smart light I've ever tried has been a total disaster. They're all sitting in storage now, or the e-waste pile.
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.
Even gov.uk has removed jQuery from its dependencies; and their browser support requirements would make a frontend developer cry.