No offense, but that's not a very sensible response. Your job may require off-hours work, but that depends largely on the needs of the company your supporting, and what you negotiate your job to be. Regardless, there's no reason why you shouldn't try to diminish the amount of off-hours work, and make it as painless as possible.
For example, let's say I have to do server updates similar to what this guy is describing, and my maintenance window is 5am-9am. The updates consist of running a few commands to kick the updates off, waiting for everything to download and install, rebooting, then checking to make sure everything was successful. Because the updates are large and the internet is slow, it sometimes takes 3 hours to perform the updates, but only 10 minutes to roll things back.
It's an exaggerated scenario, but given that basic outline, why wouldn't I just script the update process, and roll in at 8:30 with plenty of time to confirm success and roll things back if needed? What, I should still come in at 5am just because an Anonymous Coward on the Internet decided it was "part of the job"?