[merb]

I prefer plain Systeme-networkd. Basically you just create a network unit file and configure the interface with it. Basically like network/interfaces, just a little bit more cleaned up

[Faaak]

netplan can actually use systemd-networkd as a backend. It will just generate the unit files, and let systemd do the job.

[merb]

but what’s the point. It’s not that much work to create a unit file and configuration is always better in text form.

If netplan would be an api driven tool via dbus or other ipc‘s to drive an ui I would understand the need. But as cli tool?! It’s a little bit stupid

[vetinari]

NetworkManager is that api driven tool, with cli frontend available too (nmcli); I don't get the need for netplan either.

[candiddevmike]

What's the benefit over writing netplan vs networks unit files?

[DannyBee]

So that if you like to randomly switch your underlying network management tools, you can have something take what you have and generate semi-working configurations with hard to track down bugs.