So we can right back in the context we had? Who wants to spend the first 15 minutes digging out Jira, the issue you worked on, the two related ones, start IntelliJ, digging out the correct screenshots etc etc.
... or even: who wants to stop debugging and turn of the computer just because we are leaving the office to catch the train?
I first learned this on a 486/66 DX2 IBM aptiva desktop in 1995.
I've too had times when it didn't work on Linux but today boil-in-bag seems to be a Windows feature, not supported out of the box on ordinary Linux distros on mainstream hardware ;-)
This is on a Mac though, so (for me anyway) this is something that just works without any fuss.
It makes it impossible to confirm the laptop is truly off, because opening it to check turns it on. This was especially annoying during my "boarding a plane" ritual where I check everything is right before settling in.
Fridges have this problem too, but if you’re taking one of them on a plane it’s your own fault.
It will try to start up the applications I least care about; meanwhile ignoring the actual context I desire, which just slows me down more.
Something like Outlook or OneNote will restore its state reasonably well, as will Safari/Chrome/Edge/Firefox. Others, like Activity Monitor, Enpass, and iTerm2, decide to "helpfully" open a window for me even though the previous state was "running with no windows open" (which is perfectly valid for many applications).
The wifi is still connected, the ssh session I was in is still connected... The tests I was running when the doorbell rang... they pick up where they left off. It's nice.
It's stuff like this that keeps me begrudgingly coming back to Apple for laptops.
Yes and no. There have been weird issues where the machine wakes but the screen stays dark and another where externally connected monitors won’t necessarily work on wake. Possibly some of this is connected fo the hell which is the dongle lifestyle.
Apple seems to have come out the other side of these issues with recent laptops/OS releases (last 18 months).
It's the better option if you don't mind the longer time waking up, since RAM has to be restored from disk.
Otherwise, sleep should be backed by hibernation on all machines (it certainly is on mac laptops, and I think it is on windows as well): in case of power loss during sleep, the machine falls back to waking from hibernation, but if there was no power loss it wakes way faster. This is especially useful for people who move around a lot during the day and will close the laptop, move around, and reopen it. While things have gotten better with modern SSDs, having to restore 16 to 32GB from disk to RAM is far from instant-on.
I recently switched from an XPS 15 to an M1 MacBook Pro, and it's glorious that I just don't have to think about it anymore. The XPS 15 had all the problems I'm reading above, and then some.
The reason they don't write the hibernate image straight away and just power down after an hour is to eliminate writes to the SSD but I believe you can set that wait to 0.
I have a MacBook which performs this flawlessly and my Linux desktop also pauses and restores flawlessly except immediately after installing new Nvidia GPU drivers.
I haven’t thought about different CPU sleep stages in approximately 9 years when I had to make my XPS M1330 handle them in the end years of its life.
I did the same in my ~15 years of Windows & Linux desktops and laptops, with the sole exception of an IBM (yep, was still IBM) Thinkpad on which suspend to disk would magically Just Work on Linux if you created a partition at the correct location, with the correct size, and with the correct type ID. The BIOS handled it somehow, I think, which seems crazy but it did work flawlessly. IIRC I didn't even have to tell Linux about it, and I ran Gentoo at the time so I doubt it was doing anything for me automatically.
Switching to Mac a little over a decade ago broke me of the habit, eventually. It was one of many coping behaviors I didn't need anymore and had to un-learn. Unfortunately, now that I'm used to shit actually working semi-correctly a fair amount of the time (to be clear, Mac is far from perfect, everything else is just so much worse that it's like no-one else is even trying) without my having to spend time forcing it to work, it's hard to go back.