Systemd doesn't embed a webserver. It provides a service separate from both the logger and the main systemd process, which allows remote logs access. There are many issues I have with pulling various projects into one umbrella organisation, but saying systemd integrates webserver is just incorrect.

Precisely what I described. It's a web server that serves journald events/entries. It's separate from journald, and it's separate from systemd as a service. It's completely optional. It's no more embedded in systemd than nginx.

It does exist in the same umbrella project as systemd, (and I think that is an issue) but embedded is the wrong term.

> embedded is the wrong term

Don't use it then. Anyway, since systemd-the-project doesn't have a separate name from systemd-the-init, I don't see any problem with Cieplak's statement.

I'm calling it out because there are many people saying completely wrong things about systemd project. Both the init itself and other services. There's a lot of things that could be criticised about systemd, but if people constantly attack it just because they misunderstand it, it's going to be much harder to agree and change anything about the legitimate issues. Being specific helps.

So the anti-systemd trolls who harassed and attacked Debian developers until they quit are a point against systemd? Interesting perspective.