Well, that's because the "lxc" command-line tool manages LXD -- you can't use the "lxc" commands without using LXD. Arguably it should've been called "lxd-clie

Well, that's because the "lxc" command-line tool manages LXD -- you can't use the "lxc" commands without using LXD. Arguably it should've been called "lxd-client" or "lxdc" but they probably just felt it was too wordy -- most admins that used LXC and wanted to switch to LXD felt more comfortable typing "lxc <command>". And those who used LXC had no need for a top-level "lxc" command because they used the individual programs directly. Again, since the people working on the projects are the same there's nothing wrong with borrowing the name from the other project. :D