If you are referring to suspend/resume, then OpenBSD has great support[1]. Its one of the very few ACPI stacks not derived from Intel's ACPICA reference code.

[1] http://www.openbsd.org/papers/zzz.pdf (older, 2011)

Suspend and resume are basic features, by power management I mean idle and active power management, optimizing the race to zero, reclocking...

Working suspend and resume is not a basic feature as far as linuxen go.

Would you like to explain that, and maybe cite some references? Suspend and resume have been stable for me as long as I've had a computer capable of supporting them. And I'm not aware of any way to make them fail without doing something obviously intended to disable them.

Reference: Every time I've tried Linux on a laptop, Suspend, Resume, or Both has been broken in whatever $FLAVOR_OF_THE_MONTH distro/package/kernel the community insists is the next big thing.

The BSDs tend to implement these things later but far more reliably.

Never been broken on Arch, Fedora, Debian... or any of the upstream distributions I've used, when I've used them.

Your personal exacerbation of whatever imaginary and nonspecific issues you're talking about is not relevant to a conversation about people other than you.

The world doesn't need your BSD FUD. "The BSDs" is also absolutely silly as ideas go, there are BSDs which have never supported suspend/resume.

What the world doesn't need is this continuing holy war from a particularly small but sadly vocal minority of the Linux community. You really don't help the cause. I find it particularly irononic of you to accuse someone of spreading "BSD FUD" on a thread about FreeBSD. I'll 'cite' you an example of real 'FUD'; https://news.ycombinator.com/item?id=5839565

I had to install Debian on a laptop last week actually, suspend/resume absolutely did not work on it...

> The world doesn't need your BSD FUD.

You have just doomed yourself to the "I have no idea what I'm talking about" club.