Pray tell, what "polish" is contributed by systemd's binary logs that get lost in case of a crash?
Unix philosophy aside, Pottering can't be trusted to provide working software...
There are pros and cons for binary logs, they get you something (https://docs.google.com/document/pub?id=1IC9yOXj7j6cdLLxWEBA...), and you may lose something.
If you have such problems, that your machine crashes and loses filesystem data, just redirect it to the syslogd and go on.
Systemd in Linux has the same role, as Launchd in macOS. Some aspects of systemd were inspired by launchd and SMF.
Interestingly, it is a good, useful thing that contributes to polished experience when it comes to macOS, but for some reason, when someone does equivalent for Linux, it is suddenly a bad thing, just because it is different than in the past and moves the polish and experience with Linux to a higher level?