3 ms·
Yeah. It's actually funny how Pipewire and Wayland turned out. Wayland was supposed to be ready for general use "any day now" since 2011. It's 2023 and the situ
by yakubin 3y ago
Yeah. It's actually funny how Pipewire and Wayland turned out. Wayland was supposed to be ready for general use "any day now" since 2011. It's 2023 and the situation looks thus: <https://community.kde.org/Plasma/Wayland_Showstoppers https://community.kde.org/Plasma/Wayland_Showstoppers>. Whereas Pipewire seemed to have scarcely any marketing, instead it just happened. I remember reading about it for the first time at some point and started wondering whether Debian, a conservative distro, turned it on or whether I should change a setting to opt into it. I looked at htop and lo and behold: Pipewire was there. So it happened before I even heard about it, without a single hiccup, so smoothly that I didn't even notice the sound system changed.
- rcxdude 3y agoI think large part because pipewire was basically just going in with the attitude of fixing the underlying system while also supporting all the existing interfaces, which made it very much a drop-in replacement which could support pretty much all the common usecases. Wheras wayland is a big 'lets change the interface' deal (probably a good call actually) which didn't really seem to understand that it couldn't just punt on all the existing usecases for the old interface (I think there was some belief it could just be offloaded to compositor-specific APIs, which is a terrible idea guaranteed to make app developers hate you and irritate users when every combination of app and compositor acts differently), so you get a lot of breakage while people beg them to actually add standard interfaces for things.