WTF is he talking about?
Self contained user directories with the user details entombed in the directory?
Thats going to be fun for a sysadmin who wants to manage user stuff with a bit of perl. Now (s)he will have to walk through all the dirs in /home and process loads of redundant JSON stuff rather than just grep/cut/tr/sed over /etc/passwd. This seems more suited for laptops that are loaned out to users, needing their home dirs to move between machines (roaming profiles). But of course he thinks that this should be default even on a static server.
And the encryption key is in RAM when a laptop is suspended, well yep, I'm sure it is. The solution is to shutdown or hibernate the thing if you are really worried. Apple went the way of locking the key away in a special chip that greatly hinders the ability to decrypt the filesystem even if the machine is running but as PC/laptop hardware is so variable we cant guarantee the presence of a TPM, which would be the obvious solution.
I dont have much truck for Poettering/Linux. He needs to stop thinking that he knows best how EVERYTHING should be done because its been done a certain way for a long time and then helping to make it default / required. Why not improve what is already there instead of completely replacing it with brand new untested code that breaks everything? We may end up in the same place but at least it would be a development roadmap with some decent develpment and testing behind it.
Next up: Poettering creates systemd-ramcheck, not to replace memtest86 (which he will do so eventually) but to warn the user that they are not using the correct amount or speed of ram. Upon boot, systemd-ramcheck determines if you are still using DDR2 or less than 8GB of DDR3 and then puts the user into a "light boot" mode where the only function available is to launch a browser that can only browse to amazon and certain pc parts websites where you are expected to order new/more ram. Simply because Poettering thinks that nobody uses older systems or less ram and if they do they need help.
Then comes: systemd-hdddetect that does the same but with HDD's. The intention is that Poettering thinks that your machine should only be booting of an SSD as HDD's are old and slow and nobody uses them.
After that we get: systemd-guires a service that ensures that you are using the correct resolution for your monitor. When you for some reason plug in an old LCD or shock horror an old CRT that only supports 1024x768, because its a headless machine that you only need to see the gui for a moment and any display will do, you will end up with either a red flashing warning window telling yo that systemd-guires does not support anything less than 4K or the machine will attempt to switch to 1024x768, get the timings wrong so you get crap on the screen and then lock up the display manager/compositor.
I honestly think he should make his own distro, Poetter-OS to try this stuff out and then it can migrate from there.
Oh and I still have issues with pulseaudio...