USE WAYLAND

USE WAYLAND

Tip Your Landlord Shirt $21.68

Black Rifle Cuck Company, Conservative Humor Shirt $21.68

Tip Your Landlord Shirt $21.68

  1. 2 months ago
    Anonymous

    >gayland
    Nice try troony

  2. 2 months ago
    Anonymous

    I really would like to use it on every computer, unfortunately I need scaling on my 4k laptop and Wayland just can't do it (without everything looking as if I had extreme myopia)

  3. 2 months ago
    Anonymous

    Sure, after you implement the 47 missing features that I need

    • 2 months ago
      Anonymous

      I haven't experienced tearing on X in years.

      • 2 months ago
        Anonymous

        I've been booting into an xorg session with no tearfree, no compositing and no vrr for a week and I still haven't seen tearing. The screentearing that xorg is known for was a total psyop. It was probably caused by bugged drivers back in the day, because I've never seen a technical explanation of how xorg is supposed to be uniquely vulnerable to tearing.

        • 2 months ago
          Anonymous

          i have had so many god dam problems with screen tearing on my laptops. On on my pc thoug no problems at all.

        • 2 months ago
          Anonymous

          Tearing wont appear for fullscreen applications that enable vsync if you only use one monitor (browsers dont do this for videos for some unknown reason, but mpv does). And in window mode you only get tearing if you move windows around but even then it's not always noticable

    • 2 months ago
      Anonymous

      >47 missing features
      like what?

      • 2 months ago
        Anonymous

        Even fricking Python's turtle and tkinter modules do not support Wayland and requires X emulation for anything to work. Nothing works on native Wayland and anything that does needs layer upon layers of hacks to get basic functionality - like screen sharing, drag and drop and global hotkeys. Wayland is a technical dead end make by attention seeking troons for attention seeking troons.

        • 2 months ago
          Anonymous

          >Python's turtle and tkinter do not support Wayland
          So how is it Wayland's fault if the developers don't want to make their software work on it?
          >anything that does needs layer upon layers of hacks
          Except they are not hacks, but elaborately written specifications. All the functions you mentioned use the Portals Specification of Freedesktop. Some like global hotkeys are not fully implemented by desktop environments, but when they are, it should be more hassle-free (and secure) than Xorg.

          • 2 months ago
            Anonymous

            This will provoke coping and seething but wayland does not have a single feature that xorg also doesn't. There's no reason for anyone to switch, and the best thing anyone can say about wayland is that people no longer immediately notice it became the default display session (against their will) because enough of the core ideas of the project have been abandoned that it's a decent display server now. It's still been a monumental waste of time and is incapable of displacing X, because it's built on the same graphics stack. Engineering a new feature for "wayland" generally involves doing all the work in display server neutral backends like mesa or drm and then writing boilerplate in the compositor to be able to advertise protocol compliance. In any event, even when you need to do something display server specific like explicit sync, the enablement work is done in both the downstream wayland compositors and the common X backend. Wayland has nothing to offer, and can't, because the devs took the easy way out a decade ago by embracing and extending the X centric stack. It's probably why kristian hogsberg quit the project back then, he could see that wayland was doomed to becoming X12 in the worst way rather than be a whole new thing.

            >elaborately written specifications
            >freedesktop
            Come on now. freedesktop specs aren't worth wiping your ass with. Go look in your home folder to see the evidence of mozilla ignoring the xdg base directory spec for 20 years lol. Probably a dozen other programs doing the same thing too.

          • 2 months ago
            Anonymous

            >see the evidence of mozilla ignoring the xdg base directory spec
            I use multitude of programs that DO respect the base directory spec and keep their files in the prescribed places. Some of my small convenience programs I hacked in Scheme respect the base spec. Mozilla ignoring it is a show of Mozilla's hard-headedness, not a fault of the spec itself.

          • 2 months ago
            Anonymous

            >Mozilla ignoring it is a show of Mozilla's hard-headedness, not a fault of the spec itself.
            It's a show of the fact that freedesktop specs are uselessly enforced and mostly used as a bludgeon against small developers, like any other case of EEE, where the big boys weaponize the standard as a moving target. Most of corporate sponsored linux projects are like that. Mozilla themselves had no problem dropping bare ALSA support, and will probably try to drop X support, in the name of progress while themselves refusing to support pipewire properly.
            https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3608

          • 2 months ago
            Anonymous

            >used as a bludgeon against small developers
            https://wiki.archlinux.org/title/XDG_Base_Directory#Supported
            I see more small programs and developers supporting the base directory spec than bigger ones like Google's Chromium, Oracle's Java, Microsoft's Minecraft and Mozilla's Firefox and Thunderbird.

          • 2 months ago
            Anonymous

            But that's the point. Small developers are expected to support every FDO spec to the letter, while no one even thinks of enforcing them on big software projects. That's how we got the present situation of wayland by default, with devs either being misleading on purpose (gnome) about how ready wayland was vis-a-vis the protocols they implemented, or others (KDE) wildly extending the spec themselves but calling it just "wayland" like there's an xorg-like reference everything else is built on. The wayland-protocols people bikeshed good things for years on end, then like magic, race to declare a protocol as ready when some compositor hacks half of it together and unilaterally declares feature support. The original wayland protocol is so flexible as to be meaningless (i.e. vsync and compositor bypass after "every frame is perfect"), while small devs are still expected to implement asinine concepts like the wayland security model in their tiny gui app and big and obviously insecure software like firefox and steam get an aura of illusory security from using flatpak, dbus and desktop portals for everything. Just don't think about whether the browser engine itself is remotely secure.

          • 2 months ago
            Anonymous

            This 100%. Wayland only works, because it stoped being wayland and they started to reimplement X.

          • 2 months ago
            Anonymous

            >So how is it Wayland's fault if the developers don't want to make their software work on it?
            as linus would say, the user doesn't care
            it's wayland's fault if their protocol isn't attractive enough for developers to spend their own time porting their software
            I say this as someone who has actually has been using wayland for years, I have no problem with it from a technical point of view, but if some things still don't work on it after all these years it means that abandoning X wasn't justified after all and now we're stuck with two competing technologies for no good reason

          • 2 months ago
            Anonymous

            >it's wayland's fault if their protocol isn't attractive enough
            It is always going to be hard porting your software to a new system, because it requires work and nobody wants to do work unless forced to for whatever reason. Developers need to realise the advantages using native Wayland specifications in programs has for the user.

          • 2 months ago
            Anonymous

            >Developers need to realise the advantages using native Wayland specifications in programs has for the user.
            If developers "need to realise" them, they don't exist. Nobody had problems making software that used systemd modules when it was brand new and widely despised. Wayland is 16 years old.

          • 2 months ago
            Anonymous

            Why should I remake my software just to work on Wayland? At the moment it's just make once and it works everywhere but wayland decides it needs to be different from the industry standard and breaks everything, for no benefit to anyone btw.
            >Inb4 muh security
            If you're loading malware onto your computer, which will probably require root privileges' to install, you're already fricked. The display server isn't going to save you.
            >Inb4 everything will be a flatpak in some gay little container.
            The majority of flatpaks are distributed and packaged by a 3rd party (a security risk). Flatpaks containerization is a meme as well and trivial to break out of. Also for a lot of shit people just use flatseal to give it full system access because most apps barley function and are close to useless without being able to communicate with the system.

            Wayland is the most successful piece of malware ever made and has fricked the Linux desktop by wasting 16 years and millions of hours of development time. I wonder who funds this shit.

          • 2 months ago
            Anonymous

            >I wonder who funds this shit.
            Me too, who could they be?

        • 2 months ago
          Anonymous

          >Even fricking Python's turtle and tkinter modules do not support Wayland and requires X emulation
          >Legacy software requires compatibility layers
          Imagine my shock

          • 2 months ago
            Anonymous

            tkinter is an actively developed module based on the actively developed Tcl/Tk toolkit.

          • 2 months ago
            Anonymous

            >based on the actively developed Tcl/Tk toolkit.
            Lmao

          • 2 months ago
            Anonymous

            a new major version was released just last month

  4. 2 months ago
    Anonymous

    If I need to set up my PC again, I will consider.
    For now, why bother?
    Have already graphics, will have graphics afterwards.
    There is no gain, except me beeing „entertained“ while migrating.

  5. 2 months ago
    Anonymous

    no

  6. 2 months ago
    Anonymous

    electron vaapi wayland wen

    • 2 months ago
      Anonymous

      >electron vaapi wayland wen
      forgot about nvidia

  7. 2 months ago
    Anonymous

    When it's the default for xfce I will. So like 2032.

  8. 2 months ago
    Anonymous

    I'm still using xfree86

  9. 2 months ago
    Anonymous
    • 2 months ago
      Anonymous

      https://lobste.rs/s/w3zkxx/lobsters_interview_with_bjorn_stahl

      clearly a clueless individual to just /ignore.

    • 2 months ago
      Anonymous

      yeah but wayland supports gay people and that's all that matters in the end. making a safe space for men who suck other men's penises and pretend they are women.

  10. 2 months ago
    Anonymous

    Why would I? Xorg is already feature complete and it just werks, until gayland gets fully completed (15+ years at this point) I won't switch , no matter how hard FedHat shills it.

  11. 2 months ago
    Anonymous

    When did IQfy become a blatant shilling platform? I thought people just discussed fixing technology here

  12. 2 months ago
    Anonymous

    Debian will tell me when it is time to switch by shipping it as a Replaces in my dist-upgrade. Don't tell me. Tell them.

    • 2 months ago
      Anonymous

      Debian 12 already has gnome with Wayland by default, Debian 13 will ship with Plasma 6.x which would also use Wayland by default.

      • 2 months ago
        Anonymous

        I said Replaces: xserver-xorg.

        That's the bar. Don't tell me. Tell them.

  13. 2 months ago
    Anonymous

    Doesn't work well in a VM and the people who've been running Hyprland natively i've seen had screen issues so I don't really feel like moving for another decade or two.

  14. 2 months ago
    Anonymous

    I use a computer and not a """smart""" appliance, no thanks

  15. 2 months ago
    Anonymous

    Here's the thing, I'm just not gonna use it (Wayland!).
    I know... UGH, I know.
    It's just, I'm not gonna use it is all.
    HAHAHAHAHHAHAHAHA

  16. 2 months ago
    Anonymous

    >use security problems

Your email address will not be published. Required fields are marked *