Ah, you reminded me of thing c) that I encounter with Poetteringware: "Provide me with detailed examples of what went wrong... not because I'm interested in actually fixing your problem, but because I believe your complaints are fictional and you're actually engaging in character/project assassination."
The specifics of the systemd breakage were subtle, complex, undocumented, and came out as part of working on proprietary software at my day job... so even if I could remember enough about the particulars to satisfy you, I'm not sure if my NDAs would permit me to talk about it.
I do remember the NetworkManager breakage that caused me to notice that just using wpa_supplicant and friends was more than good enough, and the PulseAudio breakage that made me realize how much easier setting up jackd was than attempting to understand what was going wrong with PulseAudio.
NetworkManager: For some damn reason, the software wouldn't stop attempting to assign an MTU of zero to my interfaces that had IPv6 enabled. This caused them to get the smallest-permitted MTU (IIRC, something like 1260), and -IIRC- some rather loud complaining in the logs. I found the relevant bug report, noticed the quality of developer conversation surrounding it, and decided to find alternatives. I did... wpa_supplicant + wpa_gui/wpa_cli for my wireless interfaces and the built-in Gentoo networking config files for my wired interface (which -in practice- means "use dhcpcd to get an IPv4 address, and SLAAC to get an IPv6 address").
PulseAudio: For some reason, after a PA upgrade, it started adding in an unpredictable and variable > 100ms of latency to my audio. This required manual adjustment to mplayer playback. Burned a long time (a week? more?) verifying that the problem was just in PA, and attempting to find out what might be causing it and how to fix it. PulseAudio users were utterly unhelpful. Decided to try using jackd, which -though initially difficult to understand- I found to be far, far easier to learn to configure and troubleshoot than PulseAudio.
I've found that with Poetteringware, you're a fan... right up until the point at which it breaks and leaves you with effectively-zero information on what is going wrong and how to fix it, and/or you have a "use case" that the devs don't want to go to the trouble of handling. (This latter thing is often accompanied by assertions that the thing you want to do is a totally invalid thing that noone in their right mind would ever do, so do go away now.)
The specifics of the systemd breakage were subtle, complex, undocumented, and came out as part of working on proprietary software at my day job... so even if I could remember enough about the particulars to satisfy you, I'm not sure if my NDAs would permit me to talk about it.
I do remember the NetworkManager breakage that caused me to notice that just using wpa_supplicant and friends was more than good enough, and the PulseAudio breakage that made me realize how much easier setting up jackd was than attempting to understand what was going wrong with PulseAudio.
NetworkManager: For some damn reason, the software wouldn't stop attempting to assign an MTU of zero to my interfaces that had IPv6 enabled. This caused them to get the smallest-permitted MTU (IIRC, something like 1260), and -IIRC- some rather loud complaining in the logs. I found the relevant bug report, noticed the quality of developer conversation surrounding it, and decided to find alternatives. I did... wpa_supplicant + wpa_gui/wpa_cli for my wireless interfaces and the built-in Gentoo networking config files for my wired interface (which -in practice- means "use dhcpcd to get an IPv4 address, and SLAAC to get an IPv6 address").
PulseAudio: For some reason, after a PA upgrade, it started adding in an unpredictable and variable > 100ms of latency to my audio. This required manual adjustment to mplayer playback. Burned a long time (a week? more?) verifying that the problem was just in PA, and attempting to find out what might be causing it and how to fix it. PulseAudio users were utterly unhelpful. Decided to try using jackd, which -though initially difficult to understand- I found to be far, far easier to learn to configure and troubleshoot than PulseAudio.
I've found that with Poetteringware, you're a fan... right up until the point at which it breaks and leaves you with effectively-zero information on what is going wrong and how to fix it, and/or you have a "use case" that the devs don't want to go to the trouble of handling. (This latter thing is often accompanied by assertions that the thing you want to do is a totally invalid thing that noone in their right mind would ever do, so do go away now.)