edit: Thanks for the downvotes! I love that anything can be used as a non-sequitur to start bagging on systemd these days. Apparently it's wrong to even ask someone how this article about motd relates to systemd. I'll try to remember that.
And the entirety of systemd is an overly complex mess that does a lot of this. It tries to replace cron. It tries to replace automounters. It tries to replace inetd. It will try to replace dbus, with the aid of the kernel. It replaces everything for no good reason, and that which it doesn't replace, it consumes.
Do one thing well, work together, and handle text streams? More like do everything meh, work alone, and handle binary formats known only to you.
2. Replace it. Without apparent option. In the /etc/motd case, the problem was one of swapping a read file with a dynamic process in more-or-less the same namespace. Systemd at least advertises its malevolence.
3. Fail to adequately document behaviours.
4. Deprecate bug reports.
5. Create a fragile system within a core system context (login(1), init(8)).
Rinse, wash, repeat, rofl, weep.
I agree you shouldn't have been downed, but I DID explain in detail, as did others, why my post wasn't a non-sequitur.