Change the device? It works fine. The cable is labeled. I know where to find it. I'm not throwing away perfectly otherwise-good hardware because of that.
Sometimes it's not the cable. Sometimes it's the sodding device. I have some IP60-something speakers for the shower. Write up says USB-C power. Brilliant says I, I've got plenty of good ones I use for charging laptops and other USB-C form factor accepting devices.
Sodding things only charge with their special USB-A to USB-C cable. They're in the bag labeled "cursed usb-c charge cables".
I have content in mkv and mp4, SDR and HDR, 264 and 265. I stream from a Jellyfin container with an onboard Intel GPU passed through for transcoding as needed. The client is a 8 series NUC on gigabit using the Flatpak Jellyfin app on a Fedora 44 install. I've yet to encounter any issues with any of my library.
And potentially get fired for using unauthorised software on a corporate machine. Or find out tha USB storage is disabled (which is better than getting fired).
Physical letters do not obviate scams, nor is the cost that prohibitive. I remember actual 419 scams on blue airmail all-in-one letters back in the 80s. And that was international post too.
12‽ I'd swear the Slackware I downloaded was closer to 30+. On dialup. Via a VAX. Using FTP to go from internet to the VAX box, then Kermit from the VAX to the DOS PC using Procomm Plus. Write it all, start the install sequence, find out that the 18th disk was bad. Reboot. Rinse. Repeat.
X disks were X11. There were also the A,B, C etc disks.
Then there was the Coherent install, with massive manual on ultra thin paper with the shell on the front.
UnRaid does a variant of this; license is tied to the serial of the USB drive. It barely writes to the drive, so wear isn't meant to be much of an issue.
Tangential to this was the existence of California Software Product's "Baby/36" software. My father was a 36/400 programmer and sysadmin, and in his spare time used Baby/36 to write software for local businesses. I have vague memories of parallel port dongles being involved back then too. Don't think he mandated their use, was more a "framework" requirement.
I poked this - the 96 installer from Archive didn't play nice with wine. However, dosbox plus win3.11 and some ingmount commands worked just fine. So yes, you could export to plain text or similar.
On the note of Jupyter notebooks and version control - there was a talk at this year's Pycon Ireland about using a built in cleaner for notebooks when committing the JSON (discard the cell results), and then dropping the whole lot into a CI system utilising remote execution (and Bazel or similar) to run and cache the outputs. Was a talk from CodeThink. No video up yet though. Scenario was reproducible notebooks for processing data from a system under test.
scoot, you may find the current mini-series by the podcast Unexplainable to be interesting. It's on sound, and one episode is about tinnitus and research into it.
They also support FTP without the SSH transport, and it's not FTPS either. Various IP cameras still support FTP as a way to write files out periodically; I use this to provide a "stream" from a camera (8 seconds per frame because reasons) to the world. Actual streaming via RTSP is also available, but I could never get a stable stream to a video host (like YT or Twitch) from the camera (partially because of a poor quality network connection that can't be upgraded easily). So, FTP + credentials -> walled off directory that's not under the web root -> PHP script in web root -> web browser.
"FTP is dead" - shared web hosting would like a word. Quite a few web hosts still talk about using FTP to upload websites to the hosting server. Yes, these days you can upload SSH keys and possibly use SFTP, but the docs still talk about tools like FileZilla and basic FTP.
Anecdotally, this rings true for me. Father walked out on mother essentially, when I was in my early 40s. Rocked my world thoroughly, hadn't seen it coming. Several years of therapy to come to terms with it.