I'm worried about similar things.
Currently systemd does not get wide acceptance and is only pushed by fedora.
No other POSIX systems are going to use it.
Of course systemd has many advantages, but I don't think it's the right time to use it.
When HAL and ConsoleKit are introduced, they said similar things.
DeviceKit replaces HAL, but soon udisks replaces devicekit.
Later udisks becomes fully relying on udev and Linux-only.
After we finally fully support these *exciting* features over years, they dropped them and call them deprecated.
Now udisks is going to be replaced by udisks2, and consolekit is going to be removed.
Early adoption of new technologies can be exciting, but the result might be endless compatibility nightmare.
Systemd is such big a change to the fundamental of unix-like systems.
Personally I'll wait and see and only use it when it gets stable and supported by many distros.
Of course if somebody can make systemd support optional and turn it off by default, it's still ok.
Any comments?

On Sun, Apr 22, 2012 at 4:05 AM, Martin Bagge / brother <brother@bsnet.se> wrote:
On Sat, 21 Apr 2012, Stephan Sokolow wrote:

> How's systemd working out for you?  I like the concept, but I'm having
> trouble googling up end-user commentary on it.
> ...and I'm wary of anything lennartp produces, given that he brought us
> PulseAudio, lies to our faces that it's now reliable, and indirectly
> orchestrated this mess on my system:

This is not at all relevant to this discussion. Please refrain from
flaming unrelated software here.

For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell You.
Monitor Your Applications in Ultra-Fine Resolution. Try it FREE!
Lxde-list mailing list