Hacker News Reader

Comment by jmartinpetersen | Hacker News Reader

The article isn't really about the bug but about the (lack of) quality in the code. Spoiler alert: He doesn't like it.

"This code has no redeeming features. It must be thrown away and rewritten yet again. This time by an experienced programmer who know what error codes mean, how to use asserts properly, and most of all, who has experience at network programming."

View on HN

If the rest of the code looks anywhere near similar to the examples he shows he’s right, this is terrible code and it should never have been allowed in a serious project in this day and age.

It seems like this day and age is precisely when this sort of code is normal. We had a brief window of hopeful optimism in the mid to late 90s and even into the early 2000s, but since then it seems like code quality in general has declined tremendously.

Perhaps it's a choice between this and nothing?

Well, systemd has certainly not been accused of choosing nothing too often. Rather the opposite.

If only there were some other DHCPv6 client that we could use.

I meant that perhaps noone else came forward to do the IPv6 DHCP module coding for systemd-networkd (or whichever sub-module)? That's a question.

Rather than asking whether isc-dhcp-server over SysV, or whatever was better.

Without adjudication, it was a choice between this and init (the daemon it replaced) at a minimum.

systemd-networkd isn't a replacement for init, it's a replacement for NetworkManager/netctl/….

It's not even really a replacement for NetworkManager; it's designed to be used to provide basic networking within containers, for systemd-nspawn. It can be used on host systems, but it's deliberately fairly lightweight and designed for fairly simple configurations in containers, rather than as a full fledged replacement for other networking management daemons.

Reply on news.ycombinator.com