We are not talking about x64 vs M1 transition though. There is issues every year where developers take time to catch up.
Does the OS need to be so different that functionality of such simple devices changes to the point they don’t function?
They can, yes. I'm going through a problem on a Linux box for my job where Oracle's ACFS and ASMLib drivers won't work unless you are running a particular compiled version of the Linux kernel. In short, even kernel versioning could break a driver.
Wash/rinse/repeat for even the slightest modification to the OS that functionality of a driver could break. To go further, Snow Leopard dropped PPC support. Lion dropped x86 processor support. Mountain Lion dropped all 32bit libraries and the 32bit bootloader.
For those, the underlying OS remained the same for x86_64, so to those CPUs, that functionality was minimal, but caused devices to break to the point where they don't function.
Both me and the OH have to go through our applications and peripherals every year and make sure they all work before updating. On balance it’s worth the hassle for now. But it’s unfair to blame users who don’t want to, and I also believe they shouldn’t have to every year.
Those that don't go through that hassle also assume the risk and responsibility of those applications and peripherals breaking. They can not fault the OS for that happening, especially if they have the ability to do the work to prevent that. No-one is blaming users for not wanting to do that work; they are being called out on the irresponsibility to protect themselves, their data, and all that is needed to keep their systems working by verifying from those vendors that their applications and devices work.
If they aren't willing to do that work, they do not have the right to blame others for their own lack of work. They can't blame a gas/petrol station for not filling up their car's gas/petrol tank, when they were the ones that passed by that gas/petrol station 5-10 miles ago while their gas/petrol tank was on empty.
For a company that so heavily pushes user experience, how is the current update process a good experience? For all the issues with windows update, it’s process these days is much smoother in regards to making a restore point automatically etc. have an issue? Go to updates and hit roll back. The user doesn’t need to do any management.
Apple need to focus on adapting to lazy users as they’re starting to fall behind other systems. Though at the moment the balance of the whole package tips in their favour with laptops.
Apple has. They have placed many a warning about needing to back up their systems prior to updating, in case of any catastrophic failure. However, we're back to the proverb of You can lead a horse to water, but you can not force it to drink.
That is the problem here. No amount of Apple's focus can force a user to do what they don't want to do; therefore, the user assumes the risk and responsibility for their actions, as well as their inactions.
BL.