as I understand the referenced article, it is about tons of frustrating issues the author may have with newer systems and especially those running systemd 8) The article is not helpful at all. It just describes issues and at the end it is full of (partly) wrong conclusions.. 8) But this is just my interpretation of the content 8)
I did not mean "only" defend.. I myself always need to "defend" my decision to use systemd in our systems among my colleagues for some time now.. It is not always easy to discuss issues they have with systemd.. I am totally pro systemd - just to be clear.
What I see is that in the comments section of the article many people agree with the author. It is just my personal guess that they agree to the "things used to be easier" content.. People in general don't like changes, i think.. 8) And many people like to complain about changes they do not like.. 8) Most of the time this is not constructional (?) and does not help at all.. But please do not forget that not everybody can be a pro in system administration.
If development goes as fast as it does in systemd (and replacing init scripts, adding logind, adding journald, adding seats, adding whatever feature you can think of in only 2 years is quiet fast) some people just can not follow.. and If someone was used to add people to some 'camera' group to give them remote access to whatever, he gets "pissed" if by default only some active session gets access to it and the old way does not work anymore.. This is just human 8) What I missed in some discussion in the past was just some insight like "Hey! This article is somehow embarrassing, but.. hmm.. ..maybe he got a point (somewhere). Maybe all this stuff is not as intuitive for a 'normal' user as it used to be.." But all this can't be solved by (systemd) developers/maintainers - I guess.
What I tried to say: If someone is already "pissed", it does not help to tell him in detail
that he does not understand what he is talking about.. Sometimes it may help to mention that he is wrong and invite him to state his issues in an appropriate way on the mailing list or somewhere else and that there are people to help him to get over it 8) Things change. 8)
BTW the mailing list is great. And I personally liked the patch that changed systemd-analyze into a C program, too. And I can confirm that everybody who asks nicely always gets a competent answer to any issue they have.
And in general I agree with nearly every decision that was made during the systemd development process till now. And I like the way +Lennart Poettering
tries to explain all changes made and their background in the many blog posts..