> - socket activation was never that useful to begin with and complicates the build process for lots of services. One thing people often don't realize: socket

> - socket activation was never that useful to begin with and complicates the build process for lots of services. One thing people often don't realize: socket activation wasn't just about simplifying daemons (though it does simplify writing daemons if you don't have to deal with the non-activation case). It was also about simplifying the boot process. There exist many different system boot configurations that are difficult to express in terms of dependencies between services; for instance, depending on your particular system configuration, you might need to launch two services in different orders, because in one configuration service A will depend on service B, and in another configuration service B will depend on service A. Socket activation means you can launch the two services simultaneously, and they'll have access to each others' sockets.