Those and other big distros are better in that regard, but they're still not perfect. Depending on one's machine and needs, there can still be pain.

One recent example I experienced is jumping through hoops to get virtualization enabled in Fedora… it takes several steps that are not obvious at all. I understand not having it enabled by default since many won't need it, but there's no reason that can't just be a single CLI command that does it all.

▲

pessimizer 3 hours ago | parent [-]

Things like that can be unbelievably annoying and confusing on Windows or Macs, too. Even worse, they can just turn out to be impossible: the company can actively be preventing you from doing the thing that you want to do, refuses to give you enough access to your own system to do the thing you want to do, and/or sells permission to do what you want to do as an upgrade that you have to renew yearly.

These are things that don't happen in Linux. Doing what you want to do might be difficult (depending on how unusual it is), but there's no one actively trying to stop you from doing it for their own purposes (except systemd.)

Also, as an aside, a reason that Windows and Macs might have easy virtualization (I have no idea if they do) is because of how often they're running Linux VMs.

	▲	cosmic_cheese 2 hours ago \| parent [-]
		One needs to go a fair ways off the beaten path before they'll start running into trouble like that under macOS and Windows. For macOS in particular, most trouble that more tinker-y users might encounter disappears if guardrails (immutable system image, etc) are disabled. Virtualization generally "just works" by way of the stock Virtualization.framework and Hypervisor.framework, which virtualization apps like QEMU can then use, but bespoke virtualization like that QEMU also ships with or that built into VirtualBox and VMWare works fine too. No toggles or terminal commands necessary. Linux does get virtualized a lot, but people frequently virtualize Windows and macOS as well.