Compare that to my MacBook Air M1 which runs for a full day easily. Also, standby works.
With Dell I learned it's better to always shut down.
Compare that to my MacBook Air M1 which runs for a full day easily. Also, standby works.
With Dell I learned it's better to always shut down.
I was working almost exclusively in Office docs back then, and the Mac and Win suites were (then as now) file-format compatible. What coding I did was on *nix servers I could SSH to. And I got real, real tired of often-crashing, slow-booting, sleep-sucks Win98 on a laptop.
Then I noticed a colleague who'd come into the consulting group from the design side, and kept his Mac. He could just open it, do something, and close it. And then open it again, and have it wake up normally. It crashed marginally less often than Win98 (this is pre-OS X), but the boot time was MUCH faster, so the crashes were less annoying. I bought a Mac and have been here ever since.
And you're telling me that even today, in the Year of Our Lord Two Thousand Twenty Three, that sleep still doesn't work for shit on big-name Windows laptops? That's bananas.
There are bazillion of configurations for Windows compatible laptops.
I had both perfect and awful experience with hardware part of them. Never I misattributed the problems with the hardware to the OS.
>There are bazillion of configurations for Windows compatible laptops.
Your point?
Yes, MS, Dell, HP sucks dicjs not making it work even on a flagship notebook, but that doesn't means what there are no Windows laptops with a working sleep, it just means what you don't hear from the millions the users of thousands of working configurations... and what HP/Dell/MS just suck in the hardware department.
NB there were hundreds of laptops from HP/Dell/Asus/Acer what worked just fine. You just never heard complaints about them, because there were none.
I think it goes back to the unity of control Apple enjoys. Doesn't mean it CAN'T work for Windows, but the vendors would have to work harder to cooperate, and they clearly can't be arsed to do so.
I was borrowing a newer Surface Pro from work more recently and hoped with the additional years of development they would have managed to fix it. Sadly not.
But it was really surprising to me with the Surface Pro 3 because for years you'd been hearing "Microsoft can't make sleep work as well as Apple because they're stuck dealing with hardware and drivers from 3rd parties" and it turns out 3 generations into their own hardware venture it still sucked just as much. Connected Standby was probably a large step back even.
Huge credit to whoever wrote the standby/sleep code for Darwin for the M1s, I've never had to close my M1 Airs lid and worry about standby not working or it not resuming.
Windows is a mess and unreliable, and Linux is less said the better, it doesn't even work with secure boot on.
It seems to be a fairly significant regression in terms of functionality, which nobody really asked for, but which results in significant idle drain, coupled with the risk of a laptop deciding to resume and heat up in a bag, etc.
Apple seems to have a (long standing) positive argument here - to point at how when you put a Mac to sleep, you can resume it days later with negligible battery drain. Windows seems to have lost this in the post-S3 sleep era.
When was the last time you had a problem with SSD failure? While I’m sure it happens, I don’t see a lot of complaints from people about their SSD failing.