Should we plan on systemd ?

[Freja]

Very simply summary says, It's SELECT of "Common people oriented OS (systemd line)" OR "Expert and Computer Fans oriented OS (none-systemd line)".
Maybe it's time to select direction by Dev team?
More simple says, Generality or Quality? Need user voting?

[richb]

I guess I am a common person as I generally use systemd

[Freja]

Or, How much do we cherish neatness at MX.

That is probably "neatness priority's problem" I think.

[Eadwine Rose]

I think it is more a "what do the main devs want to do, and we'll all just have to follow" thing

[Freja]

Ah, That's true.

[j2mcgreg]

I think that we need to remember that planning and implementing are two different things. We already have SystemD as a fall back and I see no reason to change this approach.

[MadMax]

"We will cross that bridge when we get there"

As long as all programs work with SysV and the systemd-shim patches are possible and in working order, no need to change anything. It's way (like in years) too early go get as specific as a user poll.

[AVLinux]

I think we are all tempted to not only be careful and skeptical of new ideas but also we often ascribe either ill intent or a lack or reasoning to the people behind those ideas and often we make emotional judgements without (a) knowing what their intent actually is and (b) not being able to comprehend what the technical details are. In my own recent experience in working with and deploying the Enlightenment Desktop Environment I could get extremely annoyed about what I perceived to be illogical decisions but when I went to ask (or complain) to the actual developer on his IRC channel I have often felt quite foolish as he has painstakingly explained how his design intentions were not only logical but necessary to work properly and efficiently and were simply him doing the best he knows how in keeping with a completely rational larger design philosophy, no ill intent, plenty of intelligence and even the patience to explain to an uniformed User. At the end of the day Poettering and these people are making decisions based on how best to achieve the personal goals they have and to best solve the current bug or problem that they are tasked with untangling at any given moment and hopefully preventing from happening again. Perhaps these moment by moment decisions unfold in a better direction and perhaps they simply unfold in yet another way of doing the same thing, in Linux we don't have a top-level Project Manager to separate the wheat from the chaff so to speak so when you use Linux you are kind of signing up for the benefits and deficits of anarchy simply by the unrestrained nature of it's development. There doesn't have to be ill intent involved at all for this to be occasionally frustrating but at least I try now to take a breath and give the designer/developer the benefit of the doubt for simply problem solving the best they know how with skills that I'm not qualified to question or judge..

[CharlesV]

@AVLinux So well said!!

Back in 1995 I was working in a software company where the raging debate was " Heavy Design vs Nimble Coding " and as we were a windows shop, with MANY processes moving over to linux to do 'stuff that couldnt be done' in windows... it was VERY interesting to watch the entire dev crew twist around that one!

It has been VERY interesting to read and and see this topics posts! I love the community here, varied, intelligent, some very good concepts and some very good points!

[anticapitalista]

@AVLinux There are several init systems around that have been recently developed to try and move on from the weaknesses of sysVinit (which was almost 100% universal on all linux). Why do they not get any 'press coverage' let alone corporate backing?