4 ms·
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 seriou
by tinus_hn 8y ago
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.
- pbhjpbhj 8y agoPerhaps it's a choice between this and nothing?
- yxhuvud 8y agoWell, systemd has certainly not been accused of choosing nothing too often. Rather the opposite.
- NelsonMinar 8y agoIf only there were some other DHCPv6 client that we could use.
- pbhjpbhj 8y agoI 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.
- nerdy 8y agoWithout adjudication, it was a choice between this and init (the daemon it replaced) at a minimum.
- LukeShu 8y agosystemd-networkd isn't a replacement for init, it's a replacement for NetworkManager/netctl/….
- lambda 8y agoIt'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.
- deialtrous 8y agoIt 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.