• JASN_DE@lemmy.world
    link
    fedilink
    arrow-up
    1
    ·
    1 year ago

    Reporting is done by users who voluntarily upload their system specs via
    # hw-probe -all -upload

    So not skewed at all

    • KISSmyOSFeddit@lemmy.worldOP
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      1 year ago

      Do you have a better way of measuring it?
      In what direction would voluntary self-reporting of all system specs skew the display server statistic (and why)?

      • atzanteol@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Do you have a better way of measuring it?

        No better way of measuring doesn’t mean this is a good way of measuring.

            • SuperIce@lemmy.world
              link
              fedilink
              English
              arrow-up
              0
              ·
              1 year ago

              I like the way kde does it. On first install it gives a slider with how much analytics you want to send. I just do all of it because I trust KDE, but it’s nice that it asks you. They probably have some pretty good data.

            • refalo@programming.dev
              link
              fedilink
              arrow-up
              0
              ·
              1 year ago

              Well do you want useful stats or not /s

              But seriously, a lot of opt-in (that never get opted in to) data is insanely useful for developers, but it has such a bad stigma that we never get anywhere close to the amount of usefulness a larger dataset could provide.

          • atzanteol@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 year ago

            A method that attempts to collect data from a randomized or representative population rather than relying on self-report.

      • Dandroid@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        1 year ago

        I imagine people who care about this sort of thing are more likely to report it. And people who care about this sort of thing are also more likely to be early adopters and go through the effort of switching to Wayland.

        The way to get a more random sample is not something I want (built-in, automatic telemetry by default). So I’m fine with having skewed data for something like this.

      • refalo@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        1 year ago

        Because a huge portion of the people willing to do this are already on Wayland, but I believe there exists an even larger percentage on X that are not submitting any data.

        And another commenter said:

        We’re just left to do armchair psychology about the type of people who would submit data to this site. So the numbers are effectively useless.

        • onlinepersona@programming.dev
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 year ago

          Because a huge portion of the people willing to do this are already on Wayland, but I believe there exists an even larger percentage on X that are not submitting any data.

          What is the basis for that assumption?

          And another commenter said:

          We’re just left to do armchair psychology about the type of people who would submit data to this site. So the numbers are effectively useless.

          So because one cannot know which type of people submit data to the site it should be disregarded? That’s basically saying any poll or questionnaire with anonymous yet unique answers are invalid. That’s a pretty bad argument.

          Anti Commercial-AI license

          • atzanteol@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            0
            ·
            edit-2
            1 year ago

            So because one cannot know which type of people submit data to the site it should be disregarded? That’s basically saying any poll or questionnaire with anonymous yet unique answers are invalid. That’s a pretty bad argument.

            This is basically a survey or poll. You want people to provide you with data about what they’re running. To get an accurate view of the entire population you need a representative and randomized sample. If you’re relying entirely on self-reported data you’re not going to be getting a reliably randomized subset of people. You’ll get people who are motivated to report their usage to a third party. That can lead to persistent biases in the data.

            It may be that Wayland use is being under represented because the people reporting want to show that “X11 is still king!” Or it could be that this website is shared frequently with certain user groups (e.g. in some arch (btw) forum or something) and so you’re getting a skew towards that population and away from the whole.

            We don’t know who these users are and we can’t “offset” for those factors. And the data isn’t reliably randomized so it’s subject to those biases whether we know about them or not.

            Though as another person pointed out the trend itself may be of some interest if the population being polled is consistent. Though I doubt anybody suspected that Wayland use is NOT increasing?

      • chayleaf@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        by default, your content is all rights reserved, the most restrictive license possible. AI trains on “all rights reserved” content all the time. You really think adding a CC-BY-NC is gonna do anything?

    • Vilian@lemmy.ca
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      err, why? actually it can be skewed against wayland(wayland users tend to be more security aware), and why the suprise, KDE, GNOME are wayland from the get go, steam deck too, hyprland and sway etc

      • atzanteol@sh.itjust.works
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        It can skew either way equally. We’re just left to do armchair psychology about the type of people who would submit data to this site. So the numbers are effectively useless.

        • iopq@lemmy.world
          link
          fedilink
          arrow-up
          0
          ·
          1 year ago

          But the change in the numbers is not useless since the psychology of the Wayland users vs. x11 didn’t change

          • atzanteol@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 year ago

            That seems probable but was there any doubt that Wayland use is increasing? Wayland has been changing to the default distro by distro. The only reason this is “news” is because somebody has claimed that “Wayland usage has overtaken X11”.

        • ddh@lemmy.sdf.org
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 year ago

          You’re discounting the trend here. Assuming the methodology is consistent, over a short time we’re seeing a noticeable change, bias or not.

          • atzanteol@sh.itjust.works
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 year ago

            I’m not actually. Does anybody doubt that wayland use is increasing? Distros have increasingly been making it the default. I’d be surprised if use weren’t increasing. In fact it might be under-represented in this data depending on whether all distros are being accurately represented or not.

  • 3volver@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    I tried switching to Wayland on Mint, it did not go well. Unfortunately I do not care to follow an hour long guide to figure out how to get it to run games properly.

    • NamelessGO@programming.dev
      link
      fedilink
      arrow-up
      0
      ·
      edit-2
      1 year ago

      Mint Wayland support is experimental and was released in Mint 21.3 ~3 months ago

      The Wayland session isn’t as stable as the default (X11) one. It lacks features and it comes with its own limitations.

      It was added as a preview for people interested in Wayland and as an easy way for them to test if they want to give us feedback.

      A board was set up to keep track of Wayland development. It’s available at https://trello.com/b/HHs01Pab/cinnamon-wayland.

      A dedicated Github repository was created for issues related to Wayland, whether they need fixing in Cinnamon, in an XApp project, a Mint tool or anything software project we maintain: https://github.com/linuxmint/wayland.

      In terms of timing Wayland support doesn’t need to be fully ready (i.e. to be a better Cinnamon option for most people) before 2026 (Mint 23.x). That leaves us 2 years to identify and to fix all the issues. It’s something we’ll continue to work on and improve release after release.

      https://www.linuxmint.com/rel_virginia_whatsnew.php

  • nossaquesapao@lemmy.eco.br
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    Voluntarily uploaded data? This feels like that old linux user count site.

    I will run that probe on my machines to contribute, though.

  • Pantherina@feddit.de
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    1 year ago

    Crazyy!

    Btw I am XWayland free since today!

    I have a list of recommended apps here

    Some apps need environment variables:

    Qt:

    • qpwgraph

    GTK

    • GPU Screen recorder, I guess

    Electron

    • Nextcloud Flatpak
    • MullvadVPN RPM
    • Signal Flatpak
    • (Element, I switched to the Webapp in Librewolf)
    • Freetube Flatpak

    You can use xlsclients -l to detect apps using XWayland.

    Some may even want to run apps through XWayland on purpose, like KeepassXC for Clipboard access or autotype. Lets see how long it takes to implement all the needed protocols.

      • Pantherina@feddit.de
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        True, if I use bottles Flatpak as a GTK wayland app, the actual apps still use XWayland.

        Not using any Wine apps though.

        • nexussapphire@lemm.ee
          link
          fedilink
          English
          arrow-up
          0
          ·
          1 year ago

          Yeah, games are the big reason I jumped ship and I’m pretty excited about the ongoing work porting Wine to Wayland. I’m also too broke to upgrade from my Nvidia card so the efforts improving Nvidia on Wayland are greatly appreciated.

          Gotta save up for an education somehow.😄

          • Pantherina@feddit.de
            link
            fedilink
            arrow-up
            0
            ·
            1 year ago

            Yes, “just buy new hardware” is not a solution.

            But dont let some news fool ya. NVIDIA already won the AI race, so their “new open source driver” will only benefit their newly sold products

            • nexussapphire@lemm.ee
              link
              fedilink
              English
              arrow-up
              0
              ·
              1 year ago

              Yeah, thankfully I’ve got a turing card (2000 +)which is said to be the cutoff for the open source drivers.

      • OsrsNeedsF2P@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        Flatpak saved my ass when I super broke my Arch upgrade but didn’t have time to fix it before work. I ran using only Flatpak apps for like 6 weeks because they were the only thing that worked

        • Pantherina@feddit.de
          link
          fedilink
          arrow-up
          0
          ·
          1 year ago

          Funny. True, on superstable but also super unstable systems, having separated apps makes most sense.

          Not actually on rpm-ostree systems, as these have the best and most solid package management.

          • OsrsNeedsF2P@lemmy.ml
            link
            fedilink
            arrow-up
            0
            ·
            edit-2
            1 year ago

            Trying to set up snapshots is what broke my system. Not sure what the issue was exactly, but BTRFS was reporting a different amount of used space than there actually was, and my snapshots started recursively backing up until everything died

            Next time I install Linux I’m going to use Ext4 and snapshots out the gate

              • OsrsNeedsF2P@lemmy.ml
                link
                fedilink
                arrow-up
                0
                ·
                1 year ago

                Honestly, I’m kind of tired of complicated stuff. I just want a fs that works and is easy to do recovery operations on when it doesn’t work. My SSD is big enough

  • taladar@sh.itjust.works
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    1 year ago

    I wonder how representative that is of actual software used. I would imagine hardware probes are run from installers and live systems quite frequently. I would certainly not expect several percentage points of “neither” in practical settings.

      • taladar@sh.itjust.works
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        Yeah, but when was the last time you decided to upload hardware device data for a root server to some hardware survey? That is something almost exclusively done by the kind of people who want to show off their system in some way.

        • mryessir@lemmy.sdf.org
          link
          fedilink
          arrow-up
          0
          ·
          1 year ago

          Especially on servers I make sure to attend in the software packages survey. Just so that the holy-gods and kings of maintainers are aware of me, the peasant running old packages.

          No yield saya. I’m sorry.

    • refalo@programming.dev
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      I would guess not very representative at all. I don’t believe wayland usage is higher, like at all. Maybe in a limited setting like NEW installs of the most popular distros, just because they default to it. But the existing install base? No way.

      • KISSmyOSFeddit@lemmy.worldOP
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        This is a graph of recent reports (one year time frame). The total reports from all time are over 70% X11.
        But since the statistics are based on one time uploads, there’s no way to know how many of those systems are still in use, or still run X11.

  • mlg@lemmy.world
    link
    fedilink
    English
    arrow-up
    0
    ·
    1 year ago

    I’m sure Nvidia will become stable on wayland by the time xfce also migrates lol

      • refalo@programming.dev
        link
        fedilink
        arrow-up
        0
        ·
        edit-2
        1 year ago

        That’s great for you. But it also has tons of problems with a lot of other users. Including issues with proprietary drivers, XWayland compat for many apps/games, screen tearing, multi-monitor setups (esp. with different aspect ratios and/or dpi scaling factors), VRR, HDR, rotation, color management, many accessibility features etc.

      • RedWeasel@lemmy.world
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        Same here. With the exception of the explicit sync, which will hopefully be resolved this week, I have been running Plasma 6 wayland since February. And honestly when I tried the X11 version it had more issues.

    • erwan@lemmy.ml
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      I mean, by now everyone should know not to buy Nvidia hardware if you want to run Linux on it.

      It’s been more than 10 years since Linus’ finger to Nvidia.

      • IceFoxX@lemm.eeBanned from community
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        Linux is becoming more and more popular on the desktop because it is now well suited for gaming. In addition to Proton, you also have to consider all the handhelds like SteamDeck. Valve certainly doesn’t want an Nvidia product with crumbling proprietary drivers. With AMD, Nvidia could see that there is a market for it and has now established itself. It was only logical that Nvidia would not stand still. They will do everything to dominate the market as well.

      • Canary9341@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        “Everyone” who wants to be informed, but linux is also for the unconcerned or for newcomers.

        Not to mention the monopoly that nvidia has on laptops.

        • erwan@lemmy.ml
          link
          fedilink
          arrow-up
          0
          ·
          1 year ago

          I know it would be great if we could install Linux on any hardware, but unfortunately we’re not there yet.

          So you can either buy a laptop with Linux preinstalled, from a manufacturer who will support it, or do some research before hand.

          And Nvidia doesn’t have a monopoly on laptops, you can buy an AMD gaming laptop

      • Ada@lemmy.blahaj.zone
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        Bought a brand new machine. Top of the line. Installed windows on it. Thought “You know what, fuck this, time to give Linux another go”. Discovered that nvida and Wayland don’t get on…

  • Bruhh@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    Waiting for explicit sync support from nvidia but even then, I doubt I’ll switch until I can enable tearing. I’m sensitive to input latency and playing on wayland feels like my aim is floating

  • makingStuffForFun@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    1 year ago

    Anyone who needs accessibility is screwed as Wayland takes over. Let’s hope we can still choose for another say 40 years. Then, I’ll be done, and Wayland can rule. Pity those who will still need accessibility options though.

      • Skull giver@popplesburger.hilciferous.nl
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        1 year ago

        In X11, any application can control any window. That makes screen readers and other accessibility tools very easy to write.

        In Wayland, applications can only control their own stuff (no injecting sudo rm -rf / --no-preserve-root through keystrokes right after you hit enter on a sudo command in your terminal!). Screen recording access is only granted on request. A lot of applications written for the “anything goes, permissions are an illusion” style X11 has, will be difficult to port to Wayland.

        Windows had a similar problem when Vista introduced integrity levels (even non-admin users can have several levels of privileges, and windows can’t interact with higher privilege levels by default) leading to a lot of these tools running as admin, even under modern Windows.

        Wayland and X11 have a more involved accessibility tree, but not every accessibility application uses that, and not every application exposes the necessary info. Synthetic clicks (i.e. interactive screen reader support) support is limited by design, as are global keyboard shortcuts.

        Accessibility tools on Linux are already pretty mediocre compared to macOS or iOS or Android or Windows, but on Wayland it’s even worse.

        • Cyborganism@lemmy.ca
          link
          fedilink
          arrow-up
          0
          ·
          1 year ago

          Ah ok. Thank you for the detailed answer.

          I really don’t get the whole Wayland vs X11 thing. X11 works fine, why crate an alternative? What’s so great about Wayland that can’t be implemented in X11?

          • Wayland is architexturally better than X11. X11 was developed in a time where any serious application more powerfully than a terminal emulator would be running on another computer, and everything else has been hacked on top of that. There’s hardly any security restrictions for things like keyloggers and key stroke injection. It’s old and maintenance sucks for the people currently maintaining it.

            After a couple of decades, people looked at what the rest was doing and thought perhaps the old mainframe model isn’t necessary anymore. Windows and macros don’t model their GUI after mainframes with dumb terminals that happen to be physically located within the same machine, so X stands alone in its design architecture.

            I think everyone maintaining graphics code for Linux distros thinks X11 doesn’t cut it anymore. Importantly, the people writing GPU drivers don’t seem to want to be held back by the extensions built on top of X11 (while others dutifully maintain their old drivers). This is work only the companies making GPUs can afford, without it, the drivers will stop working. There’s probably also a reason Android took the Linux kernel but stripped it of X11 acceleration and developed its own GUI stack. Canonical tried to get rid of X years ago by developing Mir and a bunch of small projects tried to create an X12 of sorts, but neither took off. Almost everyone is now working on Wayland when it comes to alternatives.

            There are people who don’t care. Some GUIs will always be X11 and they can use X11 as long as the drivers and tooling still support it. Most X11 programs have worked without modification for years through XWayland, and I expect future applications to still work fine through some kind of reverse that’ll turn Wayland programs into X11 programs.

          • TheGrandNagus@lemmy.world
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 year ago

            The problem is, X11 doesn’t really work fine for modern usage.

            It kinda falls apart with multiple monitors, especially when they require different scaling or refresh rates (or both), HDR support would be incredibly difficult to add, it’s buggy, it’s virtually impossible to maintain or add features. Often fixing a bug breaks things, because the bugs in it are so old that programs have actually been designed around them, or even to utilise them.

            Now imagine trying to adapt X for use with VR/AR displays and all the differences in window management that’ll be required for that.

            It’s a security nightmare. Any app can see what any other app is doing. That means that if you have a nefarious app, it can scrape any information on your screen, without even needing root privileges. Then there’s a load of other vulnerabilities.

            The developers have moved to Wayland because X is structurally unfixable.

        • Spectacle8011@lemmy.comfysnug.space
          link
          fedilink
          arrow-up
          0
          ·
          edit-2
          1 year ago

          GNOME is working on a new Accessibility Toolkit for all desktops, funded by the $1M from STF. It’s intended to make accessibility better on Wayland.

          Watch thisweek.gnome.org for updates on accessibility; there’s usually one. Here’s a very recent article about how it’s going from LWN: https://lwn.net/Articles/971541/

          “At this point, some of you might be thinking ‘show me the code’”, he said. The audience murmured its agreement. Rather than linking to all of the repositories, he provided links to the prototypes for Orca and GTK AccessKit integration. Campbell said these would be the best way to start exploring the stack.

          If all goes well, Newton would not merely provide a better version of existing functionality, it would open up new possibilities. Campbell was running out of time, but he quickly described scenarios of allowing accessible remote-desktop sessions even when the remote machine had no assistive technologies running. He also said it might be possible to provide accessible screenshots and screencasts using Newton, because the accessibility trees could just be bundled with the image or pushed along with the screencast.

          The conclusion, he said, was that the project could provide “the overhaul that I think that accessibility in free desktop environments has needed for a little while now”. Even more, “we can advance the state-of-the-art not just compared to what we already have in free desktops like GNOME”, but even compared to proprietary platforms.

          He gave thanks to the Sovereign Tech Fund for funding his work through GNOME, and to the GNOME Foundation for coordinating the work.

          There was not much time for questions, but I managed to sneak one in to ask about the timeline for this work to be available to users. Campbell said that he was unsure, but it was unlikely it would be ready in time for GNOME 47 later this year. It might be ready in time for GNOME 48, but “I can’t make any promises”. He pointed out that his current contract ends in June, and plans to make as much progress as possible before it ends. Beyond that, “we’ll see what happens”.

          Also: https://github.com/AccessKit/accesskit

          • Like a lot of Wayland, accessibility is currently in development while distros are shipping it in production.

            I’m sure the accessibility portal will fix the current issues and even improve things, but there’s no guarantee that this will all work in a year’s time. There are still lots of restrictions right now, despite people’s best efforts to fix them in the future.

            • Spectacle8011@lemmy.comfysnug.space
              link
              fedilink
              arrow-up
              0
              ·
              edit-2
              1 year ago

              My understanding is that AccessKit is an entirely separate thing to the portal.

              Unfortunately, for several things, your choices are X, which is broken by design and few developers QA their software for anymore, or Wayland, which works pretty well in many areas, but where several important (or even basic) features are quagmired by bike shedding. But things are improving really quickly, and part of that is everyone shifting focus to Wayland.

              I recently tried to navigate my GNOME desktop via screen reader and did not enjoy the experience. If I ever need it, I hope it works properly by that point…

              At least for me, X is a worse experience on every computer I own (including the NVIDIA one), which is why I use Wayland. Neither is problem-free. I’m fortunate enough not to depend on accessibility features; perhaps my opinion would be different then.

        • makingStuffForFun@lemmy.ml
          link
          fedilink
          arrow-up
          0
          ·
          1 year ago

          This is exactly the problem I meant. Thank you for such a detailed overview of the issue. Most apps won’t provide for it, and as you described why technically, it will mean the end of accessibility as a system whole.

          • Skull giver@popplesburger.hilciferous.nl
            link
            fedilink
            English
            arrow-up
            0
            ·
            1 year ago

            I doubt it’ll be the end of accessibility. There’s a very active issue on Github about an accessibility portal to fix Wayland’s shortcomings for accessibility. I expect the problem to be that very few people work on accessibility tooling, so even if the standard is finished tomorrow, it can take years for tooling to catch up.

            I expect the Gnome/KDE tools to work on Gnome and KDE first, and then generic tools to work later. Or maybe the tooling Google has built into ChromeOS will be ported over, as Chromebooks are running on Wayland as well, who knows!

            Luckily, X11 is going nowhere for the coming years. There are still people running system-v on bleeding edge Arch installs. Linux has a very long half time when it comes to software support. If you install Ubuntu 24.04 with X11 today, you’ll be able to keep using the current accessibility toolset until 2034 at least.

    • theshatterstone54@feddit.uk
      link
      fedilink
      arrow-up
      0
      ·
      1 year ago

      Are you serious? Every sane desktop is working on accessibility. I recently heard from System76 that they’re putting in the effort for COSMIC, we have GNOME focusing a portion of that €1 million they got from Germany, on accessibility (last I heard, they’re working on cross-desktop solutions). Now, I don’t remember hearing much from Plasma on accessibility, but I think it’s fair to assume they’re also working on it.

      • makingStuffForFun@lemmy.ml
        link
        fedilink
        arrow-up
        0
        ·
        1 year ago

        User skullgiver provides an excellent answer as to why. It’s a shame, but it’s a reality that most apps won’t expose themselves properly, and hence accessibility is over in Wayland. Despite their excellent efforts.