hi all, to my understanding the above are like WINE in that they try to remedy an unideal situation and thus have to operate with older protocols. is that understanding correct or are they independent / capable of being independent

  • RustmilianEnglish
    12•1 year ago

    Pipewire is a modern audio server that can drop-in replace the mess that is alsa, pulse audio, jack, etc.

    Wayland is a communication protocol made to be a replacement for the X11 protocols, with it’s compositer implementations being the replacement for Xorg.

  • @[email protected]
    3•1 year ago

    Wait what? I’m no fan of Wayland, but what you just said, I’m afraid, is all wrong.

    1. Wayland, although being around for over a decade, is the newer protocol. The older protocol would be X11.
    2. Pipewire is also the new kid on the block, for audio. PulseAudio would be the older one being replaced.
    3. WINE is a Windows compatibility layer or wedge. It stands for Wine Is Not an Emulator, if I recall.

    Wayland seeks to provide a newer display standard, as I keep being told (forcefully and repeatedly) X11 is not sustainable… There’s a lot about that we don’t need to rehash here, but long story short, In with the new (Wayland), and sooner or later, out with the old (X11).

    Pipewire is meant to be a replacement for PulseAudio, and near as I can tell, quite backwards compatible.

    WINE is to run Windows application on Linux. Like many Linux applications right now, it is being updated to support Wayland (I believe that’s well underway already) and it already works fine with Pipewire. WINE will work on X11 and Wayland.

    Lastly, what do you mean by weaker systems? X11 is weak when it comes to being security conscious. Part of Wayland’s mission is to address that by being far more secure by default. Pipewire, while maintaining backwards compatibility, is able to do more things, as well, than the original PulseAudio.