Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Check out this discussion to know why. https://bugzilla.mozilla.org/show_b...
Basically, the ALSA API really sucks to work with. There's a fair number of bugs and device quirks and whatnot that you have to take care of as an application developer. Standardizing around PulseAudio means only PulseAudio has to care about those quirks, instead of every single application. In practice, the vast majority of users use PulseAudio; there's a small (but vocal) minority that don't. -
@rayanon understood that the change will make the maintenance easier for the devs. To be fair some distro like Arch ship with ALSA by default and it "just work" out of the box, so I'm not sure how accurate the term minority is..
P/S. The maintainer decides to include alternative build with alsa enabled for version 52.0-2 so I'm happy with it. Can't say for sure if they'll removed it for future release but I guess I can freeze the updates for now :)
Found this in our codebase, apparently one of my co-workers had written this
Just when I was about to watch the Downton Abbey clips on YouTube I realize that my Firefox went completely silent without warning.
So the latest Firefox 52.0 decided to drop ALSA and force users to use pulseaudio instead. Otherwise the only way is to recompile the source with the alsa option enabled, or downgrade.
What the actual fuck Mozilla? Who made this decision? What's the reason behind? So far Firefox is the only browser that is having the sound problem.
Nope. not another bloated package. Maybe I should switch over to Chrome.
undefined
chrome?
52
pulseaudio
alsa
mozilla
firefox
wtf