MacOS has no problem with hibernation because hardware and software are designed together: it uses TPM to manage swap encryption. I assume "BIOS" is also optimized to enable fast boot on sleep.
Linux can work with TPM but it's never as smooth. (Unless I guess you make it custom for your specific setup.)
These days with cryptenroll and friends, using the TPM is hardly an issue anymore. LVM and swapfiles both work well if you just create one large "everything but EFI" encrypted volume.
You'd need to keep secure boot on, preferably with your own keys loaded, to get all of the benefits, and that's a bit harder to automate.
Windows does all of this and more. It's harder on Linux because of a lack of tooling/interest/business incentives, and because on average Linux users want more control over their hardware than Windows users.
Windows has no problem with hibernation and FDE and it uses a swap file.
Windows and Linux run on the exact same hardware. Windows hibernation doesn't rely on secret bios features.
Unreliable hibernation is 100% and undeniably a Linux problem, there is no secret advantage or conspiracy to keep it down. It's just that nobody cares enough to make Linux not suck.
I have FDE with keys in the TPM. It's pretty smooth bit required a one time additional step in Fedora. It's also probably not very secure, but my threat model is simple theft.
Assuming things are configured correctly, the TPM would only provide the key to unlock the drive if the correct OS has been booted. Attempting to boot from a live usb to have a look at the data wouldn't work, since the TPM wouldn't present the key required.
> "we can draw our UI with additional webviews. The main reason we want to write UI using Servo itself is that we can dogfood our own stack and verify that it […]"
A general superpowered UI framework is the primary purpose of a browser, I don't see why it ever needed a second UI framework just for the chrome. Maybe HTML/CSS just wasn't up to snuff at the time.
> A shell script that checks your $HOME for unwanted files and directories.
> When xdg-ninja encounters a file or directory it knows about, it will tell you whether it's possible to move it to the appropriate location, and how to do it.
> What's even more insane is at the command line when you Tab to autocomplete the thing makes network requests and hangs! It's the only CLI app I know what requires the internet to autocomplete!
I'm pretty sure that it's a bash-completion feature / "fault".
No command is really executed while your are typing in a terminal until you press "enter".
You should take a look at Gstreamer, it has all the bells, whistles and codecs of ffmpeg (it integrates ffmpeg directly as a plugin). It's designed around the concept of graph pipelines and command line interface it's a little more verbose that ffmpeg's but more easy to understand.
reply