So far I haven't seen Mac OS force any update on me, not only that but when I accidentally activated automatic updates it showed a notification that stays on screen until you confirm/cancel the setting change.
And neither can Linux, contrary to popular belief. Anything that involves system services or god forbid the kernel requires a reboot.
Yes, if the kernel wasn't updated you could meticulously reboot each individual system service that was updated instead, but why bother when you can just reboot and be done with it?
This is not true. NixOS, as one example, is able to figure out which services (including system) need to be restarted.
> god forbid the kernel
This is not true either. Live kernel updates are possible (but are usually a paid addition, e.g. https://ubuntu.com/security/livepatch).
It might actually be a useful tool for NixOS: finding out which processes have a specific version of a module loaded, so that the user can be warned to restart those processes.
If the user wants to restart processes they can, if they want to just reboot they can also. Simply because it's "simpler" to do one, doesn't mean it's the correct universal choice in all circumstances. My wife, for example, leaves way to much crap open and leaves her laptop suspended - a restart is a serious issue for her.
That is not true at all, and anyone can confirm this by upgrading the kernel and system services (e.g. desktop environment, display manager, systemd) on Arch Linux and verifying that just about everything continues to work normally. In my experience, the only things that require a reboot are a few particular kernel modules (such as the VirtualBox host modules) and only if you are going to use those modules. Even in that case, it is still your choice whether you want to reboot.
Edit: Another classic is upgrading the kernel on Arch, not rebooting, then trying to use a thumb drive for the first time since the last boot. Since Arch uses one package for all kernel versions, only one set of loadable modules is installed per kernel package - so upgrading the package removes the loadable modules of the currently running kernel.
This is not new. I got the same notice earlier today updating a MacBook running Big Sur, which is two versions before Ventura.
you can resume in software update by clicking "Restart Now".