[klaasvakie]

So I'll prefix this by saying that I haven't used systemd for anything important yet, but have it running in a VM to see what the impact will be when the distro's force us to switch.

It seems that for the "normal" use cases (i.e. laptop running gnome+vi, server running postgres) systemd will be simpler.

For embedded / single purpose applications, it seems that it will require a chunk more work. I have use cases like a) Only power the 3G module and bring up ppp when I am within certain GPS coordinates. b) switch the wifi between hostapd and wpa_supplicant depending on the state of a GPIO.

The fact there is no general purpose programming language in the .service files makes them simpler, but for anything out of the ordinary you will be writing bash/python anyway. And then it feels like systemd is just getting in the way.

The replacement daemons also seem a bit weak, compare timesyncd with chrony for example.

Sometimes all you need PID 1 to do is run the equivalent of rc.local and get out of the way (almost like slackware's rc.M)

So I guess my point is that not everybody is in the love/hate systemd camp, some of us are just careful and still sceptical.

[andor]

I have use cases like a) Only power the 3G module and bring up ppp when I am within certain GPS coordinates.

You could create targets for all of your states, and use a small daemon to switch between them (using systemctl isolate).