It's because he implicitly and explicitly points out the very real flaws in desktop linux. And then he has the audacity to try and fix things by changing them!
If there's one thing people hate more than having flaws pointed out in something they like, it's someone else changing that thing and making it better. Not only does it feel like an insult, but it means that all that pain you went through to learn bash/xfree86.conf/ifconfig/alsactl/etc. is now irrelevant.
I don't see how you can seriously argue against systemd. The lack of integration and modernity in desktop linux has hurt it. Does no-one remember how much of a pain in the arse it was to simply connect to a WPA2 wifi network for years? That was because wifi configuration was a jumbled assortment of (really secure no doubt) shell scripts - not something that is easy to interface to a GUI. We should be celebrating the fact that someone is fixing the mess that is the linux userspace.
Anyway, none of this justifies the stupid amount of hatred inflicted on him. And I've still yet to see a sane technical criticism of systemd.
Actually, the main problem with wifi on Linux was that the drivers were crap and there were a bunch of competing WiFi stacks with mutally-incompatible APIs. If you had a decent driver, connecting to an access point and authenticating was - and still is - handled entirely by a small, single-purpose monolithic program called wpa_supplicant. The "jumbled assortment of (really secure no doubt) shell scripts" didn't need to know or care whether your network was WPA2. All they had to do was start wpa_supplicant and wait for it to tell them it had connected. Most of the complexity and issues came from older, incompatible drivers with their own built-in WPA supplicants (or no WPA support at all) that aren't supported anymore.
How are Bash, ifconfig and alsactl irrelevant? I know the second is deprecated, but obtaining debug information on network interfaces isn't something that has went away from a typical Linux distro workflow, and Bash is still the default shell on almost every distro.
Also, you won't believe how many times an "alsactl restore" has ended up fixing my audio, even on systems with PulseAudio.
If there's one thing people hate more than having flaws pointed out in something they like, it's someone else changing that thing and making it better. Not only does it feel like an insult, but it means that all that pain you went through to learn bash/xfree86.conf/ifconfig/alsactl/etc. is now irrelevant.
I don't see how you can seriously argue against systemd. The lack of integration and modernity in desktop linux has hurt it. Does no-one remember how much of a pain in the arse it was to simply connect to a WPA2 wifi network for years? That was because wifi configuration was a jumbled assortment of (really secure no doubt) shell scripts - not something that is easy to interface to a GUI. We should be celebrating the fact that someone is fixing the mess that is the linux userspace.
Anyway, none of this justifies the stupid amount of hatred inflicted on him. And I've still yet to see a sane technical criticism of systemd.