354
KDE Going all-in on a Wayland future (blogs.kde.org)
submitted 11 months ago* by to c/linux@lemmy.ml
132 comments fedilink hide all child comments
 

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.

you are viewing a single comment's thread
view the rest of the comments
[–] 47 points 11 months ago (6 children)

It’s a very Linux thing.

People get very particular about their setups.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 17 points 10 months ago (5 children)

    It's understandable on some level: if you're suddenly no longer part of the majority tribe you know you'll get fewer bug fixes and so on.

    So bullying and FUDing people into staying with your tribe could pay off.

    What I don't get is how they don't realize that they've lost. PulseAudio (through PipeWire) is here to stay. Systemd is here to stay. Wayland is here to stay.

    Maybe they just like being contrarian if they can't win.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 6 points 10 months ago (4 children)

    The main thing is that pipewire is a drop-in replacement because of how it works, wayland isnt

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] -1 points 10 months ago* (2 children)

    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?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 3 points 10 months ago (1 child)

    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.)

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 4 points 10 months ago*

    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.

  • permalink
  • fedilink
  • source
  • parent