Debian did not link OpenSSH with a 1.5 million-line library, because one doesn't exist. The library is libsystemd, which is comparatively tiny, and it is tiny so that sane things like Type=notify services get supported in more places with less pushback.

Yes, it could be smaller, broken up to remove compression support [0], what have you. But you should criticize the things that are actually problems, not some made-up bullshit about the whole of systemd being linked into everything that talks to it.

0: https://github.com/systemd/systemd/issues/32028

> Great. TFA's author thinks he cherry picked a sentence to make the project look bad.

Err... What? It's just a factual, non-judgemental description. Unlike your comment, which goes out of its way to call systemd names for whatever reason. Which just makes me less interested in what you have to say. Most people who rely on appeal to emotion to that extent are not in the right.

> systemd is a monstrous codebase and there lies shitload of exploits in it. Either intentional or accidental.

And yet...

1. practically all hyperscalers use it

2. desktops

3. container images, that power everything from docker to kubernetes use it

It helps that it's actively maintained, battle-tested as hell, and widely audited.

Point being, it's fun to hate on systemd, and maybe even hipster-like, and systemd is hardly perfect... but you are probably more likely to be exploited by a pypi or npm supply-chain attack.