• 0 Posts
  • 48 Comments
Joined 1 年前
cake
Cake day: 2024年2月4日

help-circle




  • pogodem0n@lemmy.worldtoLinux@programming.devGTK Drops X11!
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    12 天前

    You definitely should. I am running Fedora 41 with KDE Plasma and I don’t miss anything running the Wayland session. I am using it for all my gaming, university home assignments in a Windows VM, playing with local LLMs, content creation and programming. In fact, Fedora had Wayland enabled by default for nearly a decade.


  • pogodem0n@lemmy.worldtoLinux@programming.devGTK Drops X11!
    link
    fedilink
    arrow-up
    18
    arrow-down
    1
    ·
    12 天前

    Wayland doesn’t require specialized hardware though. How is it obsolescence?

    Deprecation of X11, currently, only affects cutting/bleeding-edge distributions and will, hopefully, push app developers to target Wayland properly.

    Those who strictly require features of X11 can continue using desktop environments running on it. It is not like deprecation of X11 in GTK5 will suddenly make all apps using other toolkits require Wayland.









  • If you are a little keen on learning the ins-and-outs of Linux, I highly recommend staying with Fedora. In my opinion, it has a great balance of stability and cutting-edge software selection in its repositories. The problems you have outlined are due to the default desktop environment choice of GNOME in Workstation Edition. The developers of GNOME are kind of perfectionists and have their own vision of what a desktop environment should be like. This often leads to having some common functionality most people want missing, at least without community-made extensions. KDE Plasma, on the other hand, is quite receptive to feature-requests and has all the functionality you mentioned, while being just as well supported development-wise.






  • I highly suspect the culprit is the touchpad. I have a pretty modern ASUS Zenbook laptop and its touchpad has horrible palm rejection on Linux, but works just fine on Windows. I often move the cursor to a point where a click wouldn’t do anything, like the bottom panel in KDE Plasma, or just outright disable it for that session. My guess would be that ASUS is sending nonstandard signals to the OS which is then misinterpreted by poor libinput. My next laptop will definitely be a Framework or Tuxedo, just because of this annoyance.