Re: Why user processes should persist after logout?
I do this regularly. I kick off a long-running compile, for example, then I log out because I'm going home and I'm not going to be logged in.
People have worked like this for a long time and now systemd comes along and says, no you can't do that, you must stay at work until 10pm watching your long running build run.
What struck me as especially stupid was the comment that perhaps system users should be exempt from that policy. What's a system user? The user created for that application software you just installed? You're not retrospectively insisting that application software should have its user's uid < 1000 but those uids are informally reserved for system use, not application use.
systemd needs a dose of real-life -- forcing your own desktop world view on everyone is preternaturally arrogant and stupid.