Can't a project have fuzzy boundaries yet not be an abomination? Systemd got started when trying to write a new init system and daemon manager that took advanta

Can't a project have fuzzy boundaries yet not be an abomination? Systemd got started when trying to write a new init system and daemon manager that took advantage of Linux's new cgroups features. The implementers and users of systemd decided that it made sense to implement some other things in it, to support and make those functions convenient. I think a reasonable definition of systemd's goals is "init + service manager, and then anything else which is helpful in supporting that." Yes it's a fuzzy definition, but it's not saying that it's supposed to increase in scope without bounds. For example, systemd doesn't need to provide an http daemon, because it's not helpful to other services to provide that functionality. There's httpd already. But systemd does naturally provide some date and time functions. That's because the system log functionality needs to throw time stamps on everything, and starting processes at regular intervals also relies on knowing the system time, so it naturally fits in as part of what a process management daemon should provide.