I can’t speak to what is in the minds of the Developers, but to me it’s Flexibility.
I’m manage BigFix in an Educational Medical Center with Patient Care systems, Basic Science Research systems, and Administrative systems under management. As you might be able to imagine, there are servers that we have to VERY carefully manage the reboots on. In some cases, we have to manage the time of day that the servers reboot (reboot windows must be communicated/coordinated with end users), and in others, it is a sequence issue where servers must be booted in a particular order (Server Automation helps here) for an application environment to function properly.
I personally appreciate that UNLESS I TELL an Action to reboot a computer, by default it will not do so. There are a few patches from Microsoft that have in the past forced reboots, but BigFix usually highlights this behavior in the Description for the patch.
If you want your servers to reboot at any particular stage of your patching process, you simply have to indicate it in the Action and the client will make it happen.
Then when it comes to users laptops, I like the ability to install patches with no forced reboot at the end. We display a Message to the users that their computers are beginning the patching process (don’t shutdown yet), and they get a message when it is completed. They can then choose to reboot or Cancel the reboot and do it manually. Those that forget are “reminded” by a follow-on action a few hours later.
It’s really not very difficult to manage.