3 ms·
> Like I get that PulseAudio was unreliable for many years that fostered hate Unreliable, and a shocking resource hog. Did that part ever get better, or did we
by handrous 5y ago
> Like I get that PulseAudio was unreliable for many years that fostered hate
Unreliable, and a shocking resource hog. Did that part ever get better, or did we just stop caring because memory sizes and core counts kept going op?
- jatone 5y agoneither, when pulseaudio was built there where problems all up and down the stack. from the kernel, alsa, and userspace. the effort around pulseaudio stabilized and resolved most of the problems in the kernel and alsa. leaving most of the problems in the implementation of pulseaudio. pipewire is now building off that giant amount of work pulseaudio effort resulted in and is able to reuse pulseaudio's IPC framework to seamlessly replace pulseaudio itself.
- heavyset_go 5y agoI stopped caring because PipeWire works well and ships as a drop-in replacement for PulseAudio and Jack by default.
- PaulDavisThe1st 5y agoIt's not quite a drop-in replacement for JACK yet, but I have very little doubt that it will get there.