I've never understood why people get so bent out of shape for having to restart their computer when certain updates come through.
Because I've set up a carefully crafted workspace on my system that has many programs open with many pieces of data. This workspace "lives" for days and sometimes weeks at a time, and restarting means rebuilding it all. This usually handles 2-3 client projects at a time, involving hundreds of webpages, a dozen programming projects, a few dozen file system/terminal/etc windows, and a bunch of other programs and documents.
Once set up, I can work pretty quickly and efficiently task-switch between different projects. Once destroyed I lose about an hour or two in the first day or so as I rebuild it as I work on things again. Since it's a variable environment I can't simply set up a window manager to open things on startup. The longer I work with a given workspace, the faster I get at manipulating it (right now it's small - two screens and 4 virtual desktops on this computer - the other computers are turned off at the moment, but I'll be powering them up later today for testing).
So, yes, first world problem, but I do generally hold off on restart-updates until I actually need the update, or the system needs to be restarted for some other reason. It's annoying and if I added up the time wasted and based it on the time I charge my clients it's costly, but it's not really a bad issue. Fortunately many of the programs I use do keep track of their workspace, such as firefox (History --> restore previous session), xcode, and visual studio. Wish the same was true for all the other bits and pieces I use...
It won't matter as much with Windows 8 and OS X Lion, though - all the software built to take advantage of those OS's will come back up in exactly the same state they were in prior to restarting. It will be a much more appliance-like situation.