Well, it’s more procedural than object-oriented because it’s easier to avoid object-oriented programming than procedural code :D

(Note: I wouldn’t call defining classes OOP until you start using inheritance. Overriding __str__ and stuff might count, but not a lot to me.)

Personally, as time goes on, I use inheritance less.

I switched to Emacs over two years ago because I was getting too comfortable in VS Code. If VS Code didn’t have the “dodgy” stuff, I would recommend it to everyone without reservation.

Emacs has been a pleasant surprise. The latest versions have introduced Eglot (LSP), EditorConfig and a few other odds and ends that make it very close to being usable with very little configuration. My latest suggestion for getting started is JUST two lines of config, and I think you can scale easily.

I just wish Emacs had started from the outset with more common keybindings- it makes it hard to recommend because you need to make a significant investment. I think it’s worthwhile, but still…

However, due to how it’s evolving lately, I suspect it might become even easier to get started with time. If they rolled in to base Emacs automatic LSP installation, that would be huge, for instance.

Eh, my Nextcloud LXC container idles at less than 4.5% CPU usage (“max over the week” from Proxmox). I use PostgreSQL as the backend on a separate LXC container that has some peaks of 9% CPU usage, but is normally at 5% too.

I only have two users, though. But both containers have barely IO activity.

Nope, just tested. There are hardware OTP devices that have no Internet connectivity. As far as I know, all OTP protocols are offline-friendly.

My crazy idea is: write software so that Flatpaks can run on Windows and macOS. Plus, make high-quality Flatpak-building templates available for as many programming languages, UI toolkits, etc. as possible.

Because everything that Flatpaks provide is OSS, making shims for Windows and macOS compatibility would be tedious, but doable.

Same with crosscompiling Flatpaks, compared to the difficulties of crosscompiling for Windows or macOS from any other OS, multiplatform Flatpaks should be doable to crosscompile.

So this would lead to a world where a very convenient way to package for Windows and macOS… is creating a Flatpak that works on Linux!

I’m still a huge fan of Ventoy, but lately I have been finding more and more issues with it.

So I decided to investigate using a Raspberry Pi Zero with a USB adapter to create a virtual drive:

https://github.com/alexpdp7/alexpdp7/blob/master/hardware/using-an-rpi-zero-as-an-usb-drive-to-install-operating-systems.md

It’s very wonky and manual at the moment, but I have managed to boot all Linux ISOs successfully so far. Unfortunately, I think only ISOhybrid works OOB, so Windows ISO do not work. I have found some scripts to take Windows ISO and make them ISOhybrid, but haven’t gotten around to doing that yet.

I think it should be doable to package this nicely.