Having read up on it, I don't think systemd is a bad idea. I rather like:
1. Doing away with shell scripts with huge amounts of redundant, and frequently badly written, garbage to manage starting and stopping system services.
2. Using cgroups to properly isolate, contain, and track system services.
3. Centralizing the services concept so it's network aware, rather than a separate inetd server
The major criticisms seem to be "I don't like change/I understand shell scripts" (well, true to a certain extent, but I don't think the current situation was particularly good), XML configuration (reportedly, having seen it, but yeah, XML sucks), and the developers are rude, arrogant, and assholish, which I assume means that the critics are also boycotting Linux and half a dozen other FOSS projects...
I think criticisms 1 and 2 are valid concerns and are essentially the same concern expressed twice. My belief is that there's much to be said for making configuration files as simple as possible, and to avoid manual configuration where possible. Hopefully that's what the systemd developers believe too.