Exactly. Using ridiculous namecalling for folks challenging systemd such as "immature twats" is taking sides.
Let's take a look at the full quote again...
Glad to hear. And for what it's worth, I think it's a shame some elements in the community behaved like they did. I chalk it off to them being immature twats, but mostly it's that people are people, and a good chunk of humanity are just idiots.
To me, that's calling the subset of the community who were shitty about it immature twats, not taking sides in the debate at all. Anyone can agree that there were plenty of people on both sides of the systemd issue who were most certainly deserving of the title "immature twat", so I don't have any problem with this statement.
I think you then sort of pot-kettle-black yourself with this:
It's not possible to have a reasonable collaboration so long as systemd has activist fans who do not take the time and care
to understand the criticisms.
As if the pro-systemd side was the only one with activist fans who don't understand the actual situation. Many of the criticisms have merit, but others do not and yet are continually parroted. The binary log for example, where the anti-systemd folks constantly complain that it's not ACID and that it'll be easily corrupted in a crash but never quite manage to explain how the plain text log doesn't have the same problem.
Personally I dislike systemd's breadth due to its impact on portability for those apps that would have to interact with it in a systemd environment, but I want an init system that is aware of dependencies so my boot process doesn't have to wait on something slow. As a side benefit I can have it automatically restart dependent services when something important needs to be restarted, like networking. Basically I'm not a fan of systemd, but it seems to be the only realistic chance to get what I want in an init system any time soon so given the choice between it and the status quo I say all hail our new integrated overlords.