Here's an example:
http://lkml.iu.edu//hypermail/linux/kernel/1404.0/01331.html
1. It was not a good bug report. 'Do not parse "debug" command line parameter' is not a bug. The actual bug is "assertion in systemd-journald" which is a clear regression, but independent of kernel parameters. According to comments 17 and 22, it was promptly fixed.
2. According to projects process, discussions about design are to be done on the mailinglist and not in the bug tracker. Most commenters violate this.
3. No systemd dev explained why they parse the debug parameter.
4. Sievers closed the bug report without explicitly acknowledging the assertion problem.
5. The kernel devs (especially Linus) are too hot headed and misread this. Systemd caused and fixed (!) the assertion problem.
Literally everyone with a clue in the matter seems to hate systemd with passion[1].
A long-term Debian Maintainer quit over the issue[2].
Linus himself (as you quoted) seems more than a little annoyed by systemd and its developer.
And yet somehow systemd made its way into all major distros...
Linus called out on some behaviour. That is not him saying that people should stop developing. It's him saying stop this behaviour.
Christopher Barry is most certainly not a troll.
As shown in the LKML and Debian debates, the systemd infestation was firmly opposed by nearly everyone outside the 'vested interest' RedHat filter bubble. And still is.
Some high profile names would be Eric S. Raymond or Patrick Volkerding (creator of Slackware).
Debian has been forked over this; https://en.wikipedia.org/wiki/Devuan
That is not him saying that people should stop developing. It's him saying stop this behaviour.
It's him finally calling Kay Sievers out for being incompetent and an asshole. Which was long overdue.
Sadly it's by far too late and will very likely not change a thing about systemd's "break and extinguish" strategy.
Systemd will continue to break other peoples projects in its effort to replace every mature service implementation with a hacked up systemd imitation.
At least until, hopefully, the major distros finally acknowledge their mistake and roll this disaster back.
http://systemd-free.org/