That isn't to say that it's worked out of the box. When I install Linux on a laptop, I'll put some effort into making sure everything works as wanted and this might involve adding kernel flags or mucking with dbus, and it certainly involves some research. If you expect any open source OS to behave like a proprietary OS you bought a license for, you're likely to be disappointed. If you come in with the expectation of learning to solve problems for yourself you'll fare much better.
Sleep works fine in my alder lake(12th gen) Framework on Fedora, as in it actually sleeps when you close the lid, but it won't last a week like a mac.
What do you mean?
Reliably suspending on lid close? That will depend on the system. My 12th gen Framework with Fedora is very reliable in that way.
Battery lasting a week+ when sleeping? Don't count on it but sleep time will depend on the system. Even s3 sleep varied a lot. Some systems wouldn't suspend ssd during s3, for example.
Arguably s2idle/s0ix is more mac-like, in that it is faster to sleep/wakeup than s3, which can take 6-10 seconds.
It's just not as well supported and is much more flexible, in the sense that the os has more control over what is running during sleep. Windows is supposedly takes a strategy of incrementally powering down devices as sleep duration increases to preserve battery.
What? S3 should be well under 5 seconds. 10 seconds is like a whole clean boot, or resuming from hibernation on NVMe.
How long does it take for your Intel Framework machine to sleep properly upon shutting the lid, and how long until it is ready to use after you open the lid?
I've got an old XPS 13 which works perfectly; I also got a newer XPS 15 (top of the line, 4500€) which never managed to sleep correctly (thanks to Intel s0ix hybrid-suspend) and often overheated in the bag. I got rid of the latter after 1 year, it was a mess to use.