As much as I want to support the idea of a well supported, modernised graphical protocol system, wayland simply isn’t ready yet. There’s so much shit that simply doesn’t work, and they’re all made up of little niche cases that will take substantially longer than a few months to resolve, and I still haven’t seen anything that suggests Wayland has a practical equivalent to xorg.conf.

Is Alma Linux rolling their own version of Plasma with x11? Or are they just sticking with an older version of Plasma? Is anyone else planning on hacking x11 back into the DE?


edit: To the people leaping down my throat, the last time I tried wayland was around five months ago. I have a substantial list of thi gs noted down somewhere that I was considering trting to work around or fix. off the top of my head:

  • remote desktop is a fucking pain. remmina would not allow a multiple monitor remote session at all, and a single monitor session was frequently unstable. What I really wanted was something simple that I could start from a bash script, like XFreeRDP.

  • nvidia drivers were spotty at best. I’m not too fussed about them being proprietary, but they never seemed to quite function properly. I have a 1660ti.

  • applications in general felt sluggish

  • it was hit/miss when attempting to disable desktop composition. sometimes it would cease, sometimes it would not. for skme full-screen applications, I require this as desktop composition can make input responses fairly latent. Trying to type out a class is unpleasant and somewhat halting when it takes 200ms for a character to appear after it is typed.

  • lack of a pre-init config option. I currently use a xorgconf to set screen position, layout, and resolution (including a virtual resolution) before any graphical environment starts. this stops my vertical monjtor being displayed sideways before I log in. I have yet to see something similar for wayland, but this feels like it should exist - please prove me wrong.

  • screen tearing. although the environment claims to be running my monitors at 60hz, a 60fps test sample revealed they were actually being driven at 50hz. thjs is not a hardware limitation, as all my monitors currently drive at 60hz.

  • application and desktop sharing. this flat out didn’t work. I’m told it should work, but it doesn’t.

here’s the thing. I’m not arguing against the inclusion of wayland. I’m very pleased that we have new options. I’m arguing that we should have the choice to choose the most suitable option for some time yet. I like Plasma a lot h despite it being horribly bloated, unnecessarily complex, and somehow oddly lacking in some basic features whilst simultaneously having some fantastic built-ins such as window rules.

so no, this isn’t a “self report” as one profoundly inciteful respondent put it. this is me looking for any possible solution that will allow me to run a modern DE whilst retaining features that I require.

  • doodoo_wizard@lemmy.ml
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    1 day ago

    Idk how long you’ve been around linux. Theres another old timer itt who brings up some of the things i will.

    People get popular support for saying Linus is a jerk. I never met the guy so idk. When I look back on decades of using the operating system with many components failing to be maintained because their creators couldn’t keep going, their lives changed or they simply lost interest, soulless grifters like poettering ruining the experience for the rest of us and the community in general struggling to stay afloat in the waves and eddies created by the motion of massive multinationals and governments swimming beneath our feet, I understand his behavior.

    Wayland is another in a long line of rushed rollouts that don’t consider your use case because it’s not for you.

    I truly hope someone picks up maintaining and patching plasma, but if it’s anything like past times, consider sticking with the old branch. If that seems like a dead end, maybe switch to a distribution with lts versioning.

    Remember how many people stuck with alsa until pipewire came along.

    The year of the linux desktop is gonna be a rough one.

    • anelephant@lemmy.world
      link
      fedilink
      arrow-up
      5
      ·
      1 day ago

      Pipewire and alsa are completely different things. Pipewire uses pulse/jack which then use alsa, or am I missing something?

      • doodoo_wizard@lemmy.ml
        link
        fedilink
        arrow-up
        3
        ·
        17 hours ago

        People used to use alsa directly (he’ll, I used to use oss directly).

        When pulseaudio came along it broke a bunch of stuff and had a lot of problems but there was massive institutional pressure to adopt it because everyone wanted a unified framework.

        Pipewire provides that framework and doesn’t break like pulse did. Admittedly pulse has gotten better but still sucks to interact with.

        I made that statement right after suggesting the op stick with the x11 plasma branch until a maintained fork appears.

        It’s not exactly a one to one comparison.