r0bi

Ah yes, we can now see she simply wasn't old enough yet

"Your sound card works perfectly"

Big if true.

Thank goodness for all the wonderful mass transit options then!

Oh, wait...

Werks on my Thinkpad X13

Adobe Coldfusion

Thats the app Element for the Matrix network

WiFi 7 = 802.11be, FYI

Somewhat but it was more driven on the server-side decision. I wanted something that I could set and forget, that didn't have a ton of updates but prioritized stability/security patches.

Of course, speaking of packages I do regularly use rpmfusion and epel for the extra stuff the normal repos don't have, but I understand why.

Also being a heavy user of KVM, PCIe and GPU passthrough I found the experience easier and less likely to break between updates. A lot of Red Hat devs work on these subsystems so I assume it's better QA'd.

I was running CentOS then migrated to Rocky. It handles various VMs and containers great and has been trouble free for years. 10 core Haswell-era Xeon with 64 GB RAM and a lot of ZFS storage.

I moved from Arch to Fedora on my desktop/laptop as well. Really helps my mental state not keeping up with the different distro-specific knowledge between hosts.

Thinking I am referring to using a computer as not a computer is pretty ridiculous. A computer is a tool that in capable hands can do many things not originally expected by their creators.

I generally like macOS and agree that it isn't locked down. I've used Apple computers since the Apple 2, but the first one I bought myself was an iBook G4 and later a Macbook Air. I haven't kept close attention since MacOS X went beyond version 11 though.

Certainly not an all-inclusive list but some examples off the top of my head:

• Use industry standards like OpenGL/Vulkan instead of Metal
• run 32-bit apps if I so desire
• hiding config options like monitor DPI settings
• copy media to/from iPhone without iTunes or 3rd party apps
• extend the life of hardware by upgrading components
• reducing the life of hardware by soldering the components to the motherboard
• use another voice assistant or web browser engine in iOS
• virtualize their OS on non-Apple hardware
• run emulation or virtualization apps on iOS
• iMessage
• native backups on self hosted storage

Some of these have workarounds or 3rd party apps to handle. Others may not be a problem on all hardware models or is simply a EULA matter. Or Apple has a solution for it if you buy their product for it but if you want to use your existing hardware you're SOL.

My concerns boil down to the choices Apple has made to keep you in their ecosystem and extract as much $$ as possible from their end users.

Wow, I'm not tormented at all. I guess if you don't diddle kids you have nothing to worry about...