3 ms·
This is why systemd's natural dominance of system orchestration and device initialization, and PulseAudio's natural dominance of consumer audio configuration co
by microcolonel 10y ago
This is why systemd's natural dominance of system orchestration and device initialization, and PulseAudio's natural dominance of consumer audio configuration could not be more welcome.
The big threat right now, as ever I suppose, is fragmentation in consumer desktop systems; the worst problem being Canonical's decision to develop Mir for reasons they later admitted were fabricated. The point is that all major toolkits now support Wayland quite well, but Canonical has to fight to maintain Mir support in just a subset of toolkits.
If we can get all of the system services standardized in a way which doesn't completely alienate the community; then we can move on to having standards for consumers.
- pawadu 10y agothings that have caused problems on my machine lately: 1. systemd 2. pulseaudio 3. avahi do you see a pattern?
- microcolonel 10y agoThe pattern is... you edit the default configurations of system daemons until they don't work, then complain on the internet? Wow! it's terrible that your init system has been fighting you! Let's figure out what custom unit you wrote which is causing the problem. Unless your alsa devices are broken, I find it unlikely that pulseaudio 10 will do anything untoward; if it does, well then, time to fix a bug, good thing there are so many people working on pulseaudio. Avahi... well idunno. Avahi tends to be true to the name of ZeroConf networking. I have never written an avahi configuration in my life, and yet it works for me. Maybe you have a malicious mDNS peer on your network? I'm sorry you have to experience that! If you could fire up wireshark and pass the hail mary instead of letting it drop to the green, that would be great.