systemd Breached One Million Lines Of Code In 2017

[phoronix]

Phoronix: systemd Breached One Million Lines Of Code In 2017

Systemd had a busy 2017 and its code-base is now up to over one million lines...

http://www.phoronix.com/scan.php?page=news_item&px=systemd-2017-Git-Activity

[r08z]

Disgusting.

[davidbepo]

https://i.warosu.org/data/g/img/0444/21/1411970433039.gif

[Adarion]

1 million lines... wow. That is quite a monster. Probably not all is active on every system, but it still is a lot.
Once they introduced HAL. People went with it for a while. Later they said "HAL is a large unmaintainable mess" and killed it.
I wonder if that will happen to systemD one day, too.

[onicsis]

Systemd was breached by Poettering, who breached a lot of Linux Distributions

[oldgaro]

Thanks. SystemD team!

[garegin]

Do people realize that systemd is really a suite of tools. It’s not a giant monolith. The same like GNU build tools or coreutils. So please stop saying that it’s a giant mess. What this insures is harmony within the tools. The same way all GNU utilities work seemlessly with eath other, whereas before the different Unix tools were a mixed bag from various groups of authors.
There is even a joke that head and tail were written by different devs and had different syntaxes.

[starshipeleven]

Usual clickbait bullshit. The Systemd REPOSITORY has breached the million lines. In this repo you find around 100 different tools and libraries and of course Dbus. https://github.com/systemd/systemd/tree/master/src

[emblemparade]

Do people realize that systemd is really a suite of tools. It’s not a giant monolith.

How dare you use facts against the raging mob! /s

But yes, systemd is two things: 1) an init system, which is actually a tiny little service, and nothing too radical or clever, 2) a big project including not only the init system, but also rewrites of many system services in a way that would not only integrate much better with the new init system (no more "sleep 1" farces in System V init scripts), but also work more consistently with each other, having smart and configurable inter-dependencies and with a unified system log (also part of systemd).

All in all, if all systemd components work well, it will be a huge step forward for all of us. Before systemd, other operating systems had much more robust service management than Linux. It was honestly embarrassing! To be honest, even with systemd in its current state, Windows is so much more ahead and more robust, since it has a mature init system since the days Windows NT 4. You read that right: we still have a ways to go to catch up with the year 2000 in Windows.

And no, Linux distributions do not have to use the whole project: they can just use the init system with the older components. Indeed Linux distros tend to decide on a case-by-case basis.

Any rewrite introduces regressions (bugs that have been already been solved), so it will take time to mature. If you're upset about these bugs, perhaps blame your Linux distribution for including these components before they have matured enough. Many people want "cutting edge" distros, but hypocritically the same people get angry about systemd bugs. If you want to be "cutting edge" you are essentially agreeing to beta test new software. Expect bugs.

[finalzone]

Do people realize that systemd is really a suite of tools. It’s not a giant monolith. The same like GNU build tools or coreutils. So please stop saying that it’s a giant mess. What this insures is harmony within the tools. The same way all GNU utilities work seemlessly with eath other, whereas before the different Unix tools were a mixed bag from various groups of authors.
There is even a joke that head and tail were written by different devs and had different syntaxes.

Despite all these infos provided by even UNIX veterans, some people choose to ignore them and stick to their assumptions.