Debian Developer Resigns From The Systemd Maintainership Team

[gens]

Who needs applications or even an OS when you have assembly?

how about a middle ground instead of being an extremist
not that i dislike assembly

edit:
do you have something useful to contribute,
or just "you are this/that" ?

PS "middle ground" for system programming, not for desktop apps

[erendorn]

how about a middle ground instead of being an extremist
not that i dislike assembly

edit:
do you have something useful to contribute,
or just "you are this/that" ?

PS "middle ground" for system programming, not for desktop apps

I contributed something useful, about "systemd can do stuff now without needing scripting or coding it" to which you answered "it doesn't matter 'cause you can script or code it".
I admit at that point my contributions stopped being terribly useful.

[psychoticmeow]

and i said 2 times already
"source" shell command imports functions that can be used, avoiding c/p
not to mention that a shell script can parse a config file, removing even that

Of course any time you need to change the behaviour of those functions, you've got to start copy and pasting them and that means actually learning what they do. With systemd you just read the manual and pick which configuration options suits your needs.

thus again you went to sysvinit and "scripts are bad therefore systemd is good" position
you don't remember when i said that a dependency resolving init is a good thing (even a process tracker)
and you totally forgot when i said that many inits already do it and some do it better, inits written in C (although it can be perl, python, go or anything really)

Some inits, such as? And by do it better, do you mean "do it in a script"?