It's still possible to avoid some of this. For example I've made a point to never use HDMI, and I've had no compatibility problems, e.g. I've always been able to use VGA when giving talks, etc. In fact it's usually the people with DVI/HDMI/DisplayPort/etc. scrambling to find an adapter.
I've also tried to avoid EFI and Intel processors. My previous laptop used OpenFirmware and a Geode processor, which I'm assuming never had a hidden OS/Web/etc. stack like Intel's. I eventually upgraded about 4 years ago, when the first laptop (a refurbished ThinkPad x60s) got the FSF's "respects your freedom" certification. It's not perfect, since it's got an Intel processor and I think there's EFI running underneath LibreBoot, so I've been keeping an eye out for a replacement.
I don't think we need to give up. There are some promising developments, with "bottom up" efforts like RISCV and "top down" mitigation efforts like those of Purism. 'Consumer electronics' may be a lost cause (without legal intervention, at least), but there are still options for those who prioritise digital freedom above convenience, price, etc. (e.g. Talos II)
> I've also tried to avoid EFI and Intel processors.
While your entire principled nature is worth admiration, may I ask what your objection to EFI is?
As far as I know it's an open standard, and there's nothing fundamentally bad about it.
I know lots of people have issues with UEFI Secure Boot (mostly based on FUD), but secure boot is strictly optional. Not to mention many UEFI firmwares lets you load your own keys: I.e. it respects your freedom.
Are you sure you're not accidentally conflating UEFI with Intel Management Engine (which is indeed spyware)?
> Are you sure you're not accidentally conflating UEFI with Intel Management Engine (which is indeed spyware)?
Pretty sure
> may I ask what your objection to EFI is?
> I know lots of people have issues with UEFI Secure Boot (mostly based on FUD), but secure boot is strictly optional.
I'm not the most knowledgable about this, but as far as I understand it secure boot is a hard requirement for Windows 8 hardware certification on ARM, although as you say it's optional on x86 (presumably for legacy reasons, like users expecting to have control over their machines). This is essentially the same strongarming of OEMs that contributed to killing OS/2, BeOS, etc. so the fact it's (currently) optional for certain machines doesn't quell my concern to having so much of the world reliant on Microsoft keys.
> Not to mention many UEFI firmwares lets you load your own keys: I.e. it respects your freedom.
That's not a feature I have any intention of using, and prefer to "vote with my wallet" by trying to avoid it and support alternatives.
> As far as I know it's an open standard, and there's nothing fundamentally bad about it.
Purely anecdotally/ranting, my only real experience with EFI was trying to boot from a USB stick on someone's machine (to try and recover some of their data, if I recall). I couldn't figure out how to even get a menu or anything, so I gave up.
In contrast, it didn't take me long to feel quite at home in the Forth prompt of OpenFirmware; despite never having used Forth before.
> That's not a feature I have any intention of using
Fair enough, but it is a security feature I can use to harden my system against attackers. Several Linux-distros support this OOB these days.
But if you're not interested, no pressure. Everything works fine without it.
> Purely anecdotally/ranting, my only real experience with EFI was trying to boot from a USB stick on someone's machine (to try and recover some of their data, if I recall). I couldn't figure out how to even get a menu or anything, so I gave up.
EFI is different for sure. I can't say I blame you for not wanting to read up all about it[1] when you had other stuff to do.
That said, EFI is conceptually and practically much simpler than traditional BIOS boot. It doesn't rely on magic bytes being written in specific sectors, it doesn't put a limitation on boot devices or types.
(Overly) simplified: It just says that if your medium of choice contains a file a \efi\bootx64.efi on a FAT-partition, your machine will be able to boot that thing with no further action required on anyone's part.
As such creating a bootable medium involves 1. having the right FS-type, 2. copying the files.
I haven't looked into OpenFirmware so I can't really compare, but compared to traditional BIOS I find EFI conceptually much simpler, much more manageable and to top it off much more secure.
I've also tried to avoid EFI and Intel processors. My previous laptop used OpenFirmware and a Geode processor, which I'm assuming never had a hidden OS/Web/etc. stack like Intel's. I eventually upgraded about 4 years ago, when the first laptop (a refurbished ThinkPad x60s) got the FSF's "respects your freedom" certification. It's not perfect, since it's got an Intel processor and I think there's EFI running underneath LibreBoot, so I've been keeping an eye out for a replacement.
I don't think we need to give up. There are some promising developments, with "bottom up" efforts like RISCV and "top down" mitigation efforts like those of Purism. 'Consumer electronics' may be a lost cause (without legal intervention, at least), but there are still options for those who prioritise digital freedom above convenience, price, etc. (e.g. Talos II)