Nothing to do with laziness. As other people have often mentioned on HN, in the real world of understaffed underbudget corporate IT you need to do what you can to enforce things which make everybodies life easier.
It might very well be that it is preferable to the organization as a whole to sacrifice a bit of productivity everywhere for less burden on IT. But IMHO it should not be a decision which the IT department can make in isolation.
If you are disabling things by policy, it should be after a discourse with your users and a serious attempt at training. Being a GPO dictator is an anti-pattern.
Policies such as yours are tremendously user hostile, and they are a reflection of the company's culture. I would probably not quit such a company, but I would certainly go rouge by either bringing my own equipment, or reinstalling the OS. If reprimanded, then I would quit.
I don't think this means what you think it means. I'm not a dev, but a mechanical engineer, and having to shutdown nightly, and reopen things the next morning, would cost the company at least an hour of my work time every week.