[vezzy-fnord]

systemd is targeting the totally wrong layer of the stack for such a thing. What makes a distribution is its package manager. We already have solutions like Nix for this, though they sadly might not break the mainstream if Lennart's proposed btrfs volume scheme comes into fruition.

I'd say that experimentation and divergence in systems and application software, particularly if it's easily enabled thanks to the bazaar approach of Linux, is definitely a good thing. Trying to erect unshakable foundations around what is just an OS kernel will only stifle the marketplace of ideas.

Of course, wanting a fully integrated OS is most certainly not a bad thing. This can be done either by using a BSD, or on the individual distribution level if it's sufficiently advanced.

[UnoriginalGuy]

There's no reason third party components couldn't slot into systemd. It is quite modular. It is just a different method of intercommunication, not the end of intercommunicating modular components.

[digi_owl]

Who do i hear Hotel California playing in my head?

[digi_owl]

Poettering has already laid out his vision for obsoleting package managers.

Thinks Docker style containers, applied to the whole distro. Every lib or program put in its own BTRFS based container image, and via union mount magic (managed by systemd, natch) "always" (looking forward to the blog entries about its failures) given a proper run time environment.

[asveikau]

Sounds like an idea that functions well in a niche and seems like complete nonsense in others.

The great thing about the historical diversity in Linux is that, contrary to the complaints of "pointless" differences by folks in this thread, the various distros represent honest differences of opinion about what's good in a system. If you want to do silly things with loopback mounts and containers, there's room for that in the universe, but it would be wrong to impose it on those who don't want or need it.