[ysleepy]

Ever used systemd-timesyncd or the systemd-dhcp thing, oh and systemd-resolved ? All these inferior implementations are barely configurable and lack features for use-cases outside of desktop users.

The init system is nice, but why the hell does it re-implement svchost.exe

[d21d3q]

I did. I've been maintaining python+ncurses tool for configuring system: network, ntp, etc. If you don't have dhcp server running on your network, then ifup will block until it resolves address (ui freeze). If not, then you have to kill it and also dhcp reolver. After switching to systemd-networkd it just works in background.

All configuration is done with .ini style files so that no need to use special parser for /etc/network/interfaces.

Disclaimer: I jumped on linux few years ago when systemd already had some momentum, so that I wasn't used to either init or systemd. I found the later easier to pick up.

[1_player]

systemd-resolved is inferior to what? It's the only DNS system on Linux that can handle LLMNS + split-DNS (i.e. a VPN and your LAN running alongside each other) + DNS-over-HTTPS correctly. Sure it's a pain in the arse to configure correctly, but it's more featureful than NetworkManager.

systemd-timesyncd is inferior to what? a fully fledged ntpd? go ahead, use that if you really need to, but on 99% of Linux machines systemd-timesyncd is enough.

[chmln]

All of these are optional, just disable and use an alternative?

I use resolved and timesyncd however and they work amazing for my basic needs on the laptop.