My preference here is to not have the machine sleep at all when it's closed. I do more sysadmin type work than local development type work, and having TCP (SSH) sessions end every time you close the lid would drive me bananas. I would have ruined several laptops in the last few months as our 90 pound great dane puppy has run at me while I was sitting in my chair hacking away.
MacBooks (and MBPs) don't make this easy, which (unfortunately) has kept me on PCs. I've mitigated the ten minutes of BS thing by keeping my machines clean, with an agressive attitude toward junkware, and setting the power button to suspend the computer to disk.
I've made the "i'm using you" / "i'm done using you, good night" command an explicit step this way, but after adapting it's actually kind of nice (even faster than mac sleep/wake) and lets you keep your music and remote terminals alive, which can be convenient at times.
I suspend my desktop nightly (which saves about $100/year).
I have SSH sessions to 6 machines: they just run while:; do ssh -t hostname screen -dR. After a resume, a "killall ssh" kills the broken connections and starts a new one which will bring up exactly the same terminal as before, due to screen.
Depending on how long you suspend for the SSH sessions might still work (assuming you get the same IP address, and there's no NAT with short timeouts, and there's no SSH timeout configured).
MacBooks (and MBPs) don't make this easy, which (unfortunately) has kept me on PCs. I've mitigated the ten minutes of BS thing by keeping my machines clean, with an agressive attitude toward junkware, and setting the power button to suspend the computer to disk.
I've made the "i'm using you" / "i'm done using you, good night" command an explicit step this way, but after adapting it's actually kind of nice (even faster than mac sleep/wake) and lets you keep your music and remote terminals alive, which can be convenient at times.