A very minimal or dummy Wayland server could possibly work too for games running on the console without using much extra resources for those games that requires X/Wayland
Printable View
same reason most people use Windows® maybe ? maybe some other bullshit reason, since quality of things does not correlate much with price or popularity anywhere.
indeed ! after all, console is a nice DE too.
People also complain about the pulse setup GUIs, of which there are a ton of. Your point was?
this is FOSS, and in FOSS you don't have to be an Alpha-tester, unless you want to.
i know better one thing for sure: _i_ _know better_ what _i need_.
i may crunch though many things, but refuse to deal with systemd in state it is now. but i may give it a chance once it matured enough. i don't need it, because i have better-suited alternatives, but i might want it someday.
pulseaudio is another story, for me: it's 100% useless and counter-productive to some extent. i don't need "something better", i don't need it, and i don't have a need to need it. i may _tolerate_ it, if it would start targeting all sound hardware and not just shitty notebooks's built-in HDA chips though.
and i don't hate Lennart, i hate more featureless and glitchy software and attitude of people, who make and cram it unto user masses.
i dislike policykit, nepomuk and its creators the same damn way as pulseaudio's.
but, from my point of view, kmscon's and wayland's guys have more decent approaches. i want their stuff, and don't mind needing it in the future.
PS: thank Daniel i'm using Gentoo and don't have PA installed and systemd activated. but that doesn't mean, i don't have a right to express indignation about it.
no, it's not fun.
but maybe you can enlighten me if & how i can set up 2 _independent_ stereo + 1 mixed-on-the-fly-from-stereo-to-mono outputs for various programs's _simultaneous_ use, having only built-in motherboard's HDA with "standard" 6 holes (4 for 7.1 setup, Mic In, Line In) and using only pulseaudio and its GUI tools, huh ?
also, maybe you have some examples of things that cannot be done with existing alsa's GUI tools but can - with pulseaudio's ?
because, that what i asked above indeed can't be done with alsa's GUI and only with manual alsa config writing. i'm not aware however of any way to do it with pulseaudio, let alone _easier_ way. and everything else i need from sound system, on the contrary, can be done with alsa GUIs.
_
the only thing, that i see, pulseaudio is good for now is dumbing down potential features of alsa & hardware at hand to "input to everything from single input hole plugged and output from everything to every output plugged of one selected device with memory of volume level per each device (remembering volume levels for each channel of each device ? forget that !)", which doesn't make existing things easier to use, but enables ignorant not to be overwhelmed by possibilities by eliminating those things.
which is quite fucked up. and a popular way to do things these days :/
damn, i dream of the day PA's GUI would be made that wlll be able to automatically repressent all the possibilities of alsa usage for any configuration of alsa-supported sound devices, utilising all hardware-features and alsa software-features ! then i will be motherfucking impressed !