LPC: Linux audio: it's a mess

It's not that you're bashing Lennart, it's more that you're basing your
bashing on content-free innuendo. *Why* doesn't network-capability belong
in 'the mass of machines'? Why does the pulseaudio native network protocol
*plugin* 'introduce[] bugs and eat[] memory and cpu'? Got any evidence? I
doubt it, because there is none. (I mean, yes, obviously deserializing
data flowing over the network costs a bit of CPU time, but it's utterly
insignificant, and you don't even pay that cost unless you're doing
network streaming.)

I don't even know what your criteria for measuring 'performance' are,
given that your examples are matched by pulseaudio (given hardware that
supports hi-res timers, at least).

Personally I use Pulseaudio for one reason: *API compatibility*.
Pulseaudio can emulate virtually everything (other than Jack) so I don't
need to run a mass of battling incompatible sound daemons anymore: I can
just run one. (And yes, it *can* mix stuff from multiple sources and sinks
freely.)

The rest of your post is sub-Slashdot ad hominems that aren't worth
responding to.