5 ms·
Honestly, I get it. Alsa is not the future, unless someone steps up and maintains it. And it looks like that's not going to happen. I firmly believe that we sho
by CaptSpify 10y ago
Honestly, I get it. Alsa is not the future, unless someone steps up and maintains it. And it looks like that's not going to happen. I firmly believe that we should move on.
But part of moving on requires that we look at PA's problems. Everytime a PA thread comes up, people disregard and yell at everyone who has a problem with PA. PA has a bad reputation for a reason, and it's not just Pottering hate (though that's likely part of it). It's that PA is not good software. It needs to be fixed. And until it is, you'll have people wanting to go back to software that "just worked".
- AstralStorm 10y agoWrong. ALSA is the main Linux audio backend. PulseAudio cannot output to sound devices without it. (only to network) So not supporting it is akin to not supporting audio output on Linux. Dropping PulseAudio is fine if they want to reduce maintenance load, as it is optional, unlike ALSA.
- majewsky 10y agoHave you looked at the actual APIs? After last week's announcement, I talked to a friend who has, and apparently the PulseAudio API is much more straight-forward than the ALSA one. He voiced understanding for Firefox supporting PulseAudio instead of ALSA. EDIT: Also, arguing that Firefox needs to support ALSA instead of PulseAudio because "PulseAudio cannot output to sound devices to ALSA" is similar to saying Firefox should be able to issue SATA commands directly because filesystems would not work without that.
- AstralStorm 10y agoNo, VFS is a valid kernel interface, as is ALSA. Your analogy is wrong and pointless. This is more similar to removing all support for files and requiring everyone to install MySQL.
- majewsky 10y agoMy argument still stands. There is no law against using user-level interfaces and abstractions that wrap those provided by the kernel.