>No, not really. Take xfce
Xfce has a settings window.
>>has no firewall control
So you're going to also write an iptables front-end? Do you know how much work that takes? Take a look at firewalld. Only a complete fool would do that and it's way out of scope for a desktop environment.
>>no control or printer daemon
Same as above.
>Stability, mainly. I encourage isolated libraries so when some program maintainer decides to fuck shit up, I don't want my themes to get fucked. Furthermore I want to implement OSX's ~/Apps directory for the explicitly installed gtk/Qt apps so people can drag-drop and install/remove a software easily.
That has nothing to do with a desktop environment. That's on the distribution layer.
>Name ONE DE (apart from KDE with akonadi server) that has a synced daemon.
That is almost out of scope for a desktop environment. I don't even know what you mean with a "synced daemon", but I can tell you that you're way better off using a standalone program for that.
>False. KDE and GNOME stuck to the freedesktop but cinnamon, budgie, pantheon fucked shit up.
I don't use the latter environments, but components from them. They all seem to respect freedesktop standards. My file manager, Cinnamon's, respects the XDG directories for example.
>Anyways, logind, bluetoothctl, networkd, systemd-mount, systemd-resolved, acpid can be utilized through the control centre effectively thanks to the standard init system.
Those are components under the systemd roof. Stop calling it "init system", because it's not just an init system. Also, at least one of those things isn't related to systemd, acpid.
I don't even know why I'm bothering with this, because this will never happen and even if it did, it doesn't affect me in any way. Do you have a logo yet?