I heard once in a Windows Update talk (probably a BUILD talk I watched on Channel 9?) that the Windows kernel needs far fewer restarts than people assume; Microsoft just doesn't trust most application software in user space to continue to work if they silently swapped kernel components out from under it. Too much software does dumb things with system state or makes wrong assumptions about system calls (despite stacks of manuals telling them otherwise).
The UWP application lifecycle model is built to support the kernel asking an app to pause, save what state it can, and restart at some point later with just a hint of its previous state. So many programmers seem to hate it (and get it wrong) because it means they have to think about state management more than they ever had to before.
That API was informed by the need to restart individual applications without rebooting the entire system. If more apps followed the UWP application lifecycle well, Windows would need fewer reboots.
(Compare to the Xbox One where developers were not given a choice to opt-out of the UWP application lifecycle, and it having mostly just two forced restarts a year. Also note how many game developers and app developers get the UWP application lifecycle wrong and you find games/apps in broken states when you get back to them, requiring a force quit.)
The easiest thing to change is your habits as a user and make sure that reboots aren't a problem to you. Windows 10 gives a lot of warning (more so now than at launch, of course) when reboots are coming up, including not-subtle things like system notifications, and subtle places like wording changes in the Shutdown menus as updates approach (first "Restart" becomes "Update and Restart", then as the deadline looms closer, "Shutdown" becomes "Update and Shutdown"). Find software that saves more state between restarts; encourage applications to move to the UWP application lifecycle (and use it correctly); checkpoint your work more often; speed up your startup and eliminate everything you can from the critical path (sorry, Slack, you can wait a few minutes after I've finished booting; I don't need my Windows Service that performs backups to run Automatic, it's fine to be Automatic (Delayed) delay started by Windows). Those are all things you can do proactively instead of being angry at Windows needing to restart because it is overly-worried your applications will break in mysterious ways if it doesn't.
