I think I see the problem we are having here in the thread.
- Your concerns are valid
- Our concerns are valid
- We see your point, but do not seem to care
- Both sides have different ways to deal with such problems
That the spread of
systemd will be a problem for desktop usage is clear. BUT - many here do not use desktop environments, and thus don't care. Effort to gain ratio says you should go play with the kids instead. Most users here have an engineering background and, that is important, some experience in the field. They see
systemd as one of the many many "oh look, shiny" projects out there. While Linux went from
MAKEDEV to
HAL to
udev (now part of
systemd), *BSD went to
devd and was done with it. All these
*Kit packages (I think of BeOS when I hear these mentioned) are also being replaced. And the same will be done with their replacement.
Standard engineering practice is to first check if a problem
has to be solved. We do not have enough resources to hand this out to someone, there are more important things to do. That is the way engineers think, when they can think for themselves.
- Can this be solved?
- Can I solve it?
- Why should I?
- What would the benefits/contras be?
So before you think nobody understands what you want and run off - we do understand. We simply have a different mind set. We have some priorities, and we have some experience. I tried to point that out when I said that it might not be in the best interest of the desktop environment people to utilize
systemd in any substantial way. It might save work
now (short term gain) but is likely to cost them dear in the future when the makers of
systemd do things to break stuff (been there, seen it).
You are welcome to work on the task, we will help you. But we will not gather around some banner for this. At least, I won't. Nothing personal, that's experience.
:beer
