So your problem is that you haven't spent enough time learning to configure your ssh according to your needs. The cool thing is that ssh configs can be done for a specific session (if it happens just once in a while or you experiment about the right configuration), it can be done per target (in case you want to react differently on your personal blog and your company development host), and globally (to apply always). Have fun reading. You may find that ssh can solve a lot of problems and in some people's mind even solves problems like other tools but more elegant (I personally prefer it over http-proxys and VPNs as well).
Making it explicit means you have more control about what will continue to run.
I wonder if this breaks mosh as well, if it's anything with per-user persistence.
* https://github.com/mobile-shell/mosh/blob/master/src/fronten...
Systemd’s change is just "processes have to explicitly declare they are long-running, or they’ll be killed".
How else would you do it?
This is basically sandboxing time itself.
The bad software will never be fixed. Never. But you can put it in a jail, and let the user configure that good software won’t have that jail.
Most systems have a single human user anyway and there is no need for them to log out. For systems that have multiple users it seems more convenient to be able to pick up where you left off.