cross-posted from: https://lemmy.world/post/39342270
Well folks, it’s the beginning of a new era: after nearly three decades of KDE desktop environments running on X11, the future KDE Plasma 6.8 release will be Wayland-exclusive! Support for X11 applications will be fully entrusted to Xwayland, and the Plasma X11 session will no longer be included.
The main thing is that pipewire is a drop-in replacement because of how it works, wayland isnt
xwayland makes things a near drop in replacement for wayland and people still complain.
What made you think that that’s a relevant answer?
I specifically said PULSEAUDIO is here to stay, you know, as opposed to manually managing a trillion ALSA devices.
Then I mentioned PipeWire to placate the nitpickers who would point out that PulseAudio (the implementation) isn’t actually around anymore, only the device management paradigm.
And somehow you honed into that word, completely ignored everything around it, and said some stuff that sounds vaguely related to the topic at hand, yet has no actual meaning.
Why?
I still have almost no idea what PulseAudio and PipeWire even do, aside from them being two of five(!) different audio-related subsystems that any given sound problem might be related to. (The others being OSS, ALSA, and JACK, which I also don’t understand.)
OK, let’s see if I remember well:
OSS is obsolete.
ALSA is a basic primitive way to do play audio streams integrated into the kernel.
PA is an abstraction on top of ALSA that helps with network stuff, per-application volume control, …
JACK is an alternative to ALSA/PA for low latency professional use cases: you can plumb it yourself, connect inputs/outputs, …
PW is an efficient implementation of both PA and JACK, which is better than the original PA in latency.