There's the opposite. If it doesn't disable suspend, it is not a work computer.
my work macbook will close all the network connections/compile/rendering when i close the lid to walk from meeting to meeting (or used to. seems like the universe closed this bug as 'WONT FIX')
I have no decent UX to disable that when i need my network connections/compile time/render time/etc... It's either sleep enabled and i can't risk touching the lid, or complicated arcane steps to break sleep and allow me to carry it.
Macs in the last decade are like windows computers in the late 90s.
Every single little obvious feature depend on a shaddy shareware app running on your taskbar.
want to close the lid? amphetamine. Want to copy paste history? copyQ. Want per-window alt-tab? Switch. Want to be able to change the volume? soundflower.
i have some twenty icons there now. And that's not even counting the chrome ones to disable features i don't want on the browser. sigh.
It suspends/resumes just fine as long as your OS supports it. The issue is that you need much better runtime power management since it's now up to the OS to put parts in a low power state rather than relying on the firmware to do it.
No. Modern firmwares usually support S3 just fine - but it's patched away to make "modern standby" work more easily from the perspective of the hardware manufacturer.
With enough whining (ex: the Thinkpad community), the manufacturer can be convinced to replaced their half baked solution by something slightly better.
If you do not care about TPM, you can also patch your ACPI tables yourself.
my work macbook will close all the network connections/compile/rendering when i close the lid to walk from meeting to meeting (or used to. seems like the universe closed this bug as 'WONT FIX')
I have no decent UX to disable that when i need my network connections/compile time/render time/etc... It's either sleep enabled and i can't risk touching the lid, or complicated arcane steps to break sleep and allow me to carry it.