Presumably he meant the laptop didn't go into standby when closed or woke up from standby while still closed.

Just want to warn other readers: Not all framework models have S3 sleep. I've got the 7040 AMD framework laptop and it only does s2idle.

Halting power until an external physical event seems like a simple enough idea. I have never wanted to close my laptop and let it keep number crunching.

That's due to "connected standby"[1], which is to have laptops behave more like a phone when in sleep. This is in contrast to S3 sleep, which basically halts all activity. Sounds all good in theory, but as soon as you allow code to be run while in sleep, it's easy for some runaway app (OS or third party) to eat through your battery even while your laptop is "sleeping". Worse is that there's no way to force sleep, so your only choice is hibernate, which is even worse than S3 sleep before.

[1] https://learn.microsoft.com/en-us/windows-hardware/design/de...

So anyway that killed one of my laptop's batteries. So much for supporting Internet freedoms...

Windows comes with a utility that'll tell you what process denied a sleep request, super useful.

I've actually ran into MacBooks not sleeping a few times, but it is much rarer.

It is unfortunate because back on the mid 2000s windows had the best functioning sleep code, but then they tried to catch up with iPad's # instant on and chasing perfection led to the current mess.

Much more likely is that the OS was prevented from going to sleep by some badly behaved process, or got woken up by another thing like allowing USB to wake it from sleep, where even touching the mouse can wake it - with some laptop equivalent like a ghost touchpad touch or whatever.

No, it's really not. You know, evidenced by the fact you have to manually post every fking reply link, individually, for the non-siccophants among us to be able to read it?

You simply see what the author posted and people's reactions.

It also doesn't load 400MB of JavaScript or whatever.