I've had to batch-rename files many times over the years. That means:
1. I do it manually over however many minutes. Works if there aren't too many (especially if the pattern is too complex to trivially automate).
2. I make a Python script for it. No way I'm renaming a thousand files by hand.
3. I don't do it. Too much work. The problem lingers forever.
Or these days,
4. I make an AI datacenter eat another town's water supply.
I've never used Emacs. I tried vi(m) nonconsensually and had to google how to exit. A while later, I tried it intentionally and hkjl navigation didn't work because I use a custom keyboard layout, so I never touched it again. Sublime Text and its many cursors for the win!
I'd love a way that isn't miserable to do such a common basic task.
Yes, they're way better now! The quality was poor because they were using decades-old original IBM tooling, and injection molds don't last forever D:. But, they made new molds in, I think, 2020? I bought a New Model M in 2021. Mine has a custom-printed layout, and it looks stock, not just some one-off. The plastic chassis is sturdy and doesn't need any sort of filing. It's been my daily driver ever since and is my favorite keyboard I've ever used, so I happily recommend them to any typing enthusiast. Sooo much better than Cherry switches (or, dog forbid, "office" keyboard rubber domes).
An internal combustion engine may be complex, but it's not fancy. I can see and touch and understand every part of it. I can maintain and modify and repair it. This is not true for fancy electronics and certainly not locked-down proprietary firmware.
Change your network name. When the TV prompts you to connect, join the renamed network. Then, rename it back so everything else can connect again and the TV can't. I can think of a few potential problems with this, but, it might work?
Or blacklist the TV's MAC address in your router settings. Didn't think of that first for some reason.
Simple: A version specifier, or feature specifiers. Backward compatibility concerns vanish when I can opt-in to a newer spec. Old code keeps working, and new code doesn't suffer for legacy nonsense.
Sadly, the closest I've personally seen to this sort of thing in widespread use is `"use strict";` in JavaScript, which is only a single binary switch. You can't, say, turn on a new keyword, disable a keyword, switch to a different incompatible version of some browser API, etc.
I encourage all language designers to include a feature mechanism in a forward-compatible way. Don't overthink the difficulty: It doesn't need to do anything at first, it just needs to not be a parsing error. Treat it like a comment. FYI, this is the same as having a version number or header size in a binary file format's header, which all sane formats have (there are a lot of insane formats out there...).
1. I do it manually over however many minutes. Works if there aren't too many (especially if the pattern is too complex to trivially automate).
2. I make a Python script for it. No way I'm renaming a thousand files by hand.
3. I don't do it. Too much work. The problem lingers forever.
Or these days,
4. I make an AI datacenter eat another town's water supply.
I've never used Emacs. I tried vi(m) nonconsensually and had to google how to exit. A while later, I tried it intentionally and hkjl navigation didn't work because I use a custom keyboard layout, so I never touched it again. Sublime Text and its many cursors for the win!
I'd love a way that isn't miserable to do such a common basic task.