[_cenw]

Modern Standby. Windows wanted to do the Apple "power nap" stuff, but never realized how painful it'd be if you don't control all the hardware and have millions of different hardware permutations (with a lot of terrible drivers) instead of just a few. Not that it would've helped, half the time my machine is either overheating or off it seems to be wake timers doing windows updates (which yes, you can disable, but most wouldn't).

I don't get why S3 sleep had to die for this, but it did.

[lillecarl]

I'm super happy with S0 on Linux. The implementation is all about doing as little as possible but effectively remain "on".

[vladvasiliu]

What's the point, though? If it doesn't actually do anything, why keep it on?

[lillecarl]

Because you don't have to reinitialize hardware if you don't shut it off. Which is hard and causes problems. It's easier to just go into power saving++.

If you want your device to be off, power it off.

[jorvi]

> Windows wanted to do the Apple "power nap" stuff

On Linux, you can run a systemd unit file that will trigger `rfkill` on sleep and a different `rfkill` invocation on wake and you effectively dodge all that crap because the laptop isn't connected to WiFi and thus will sit around realizing its spinning its wheels and wil shut down further down the s0 chain.

> I don't get why S3 sleep had to die for this, but it did.

Worse yet, the dirty little secret is that many laptops that offer both S0 and S3 will actually drain more energy in S3 than in S0 because the S3 mode has had poor QA.