this post was submitted on 29 Jan 2026
115 points (88.6% liked)

linuxmemes

29258 readers
1793 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
  • Don't get baited into back-and-forth insults. We are not animals.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn, no politics, no trolling or ragebaiting.
  • Don't come looking for advice, this is not the right community.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
  • 5. πŸ‡¬πŸ‡§ Language/язык/Sprache
  • This is primarily an English-speaking community. πŸ‡¬πŸ‡§πŸ‡¦πŸ‡ΊπŸ‡ΊπŸ‡Έ
  • Comments written in other languages are allowed.
  • The substance of a post should be comprehensible for people who only speak English.
  • Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
  • 6. (NEW!) Regarding public figuresWe all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations.
  • Keep discussions polite and free of disparagement.
  • We are never in possession of all of the facts. Defamatory comments will not be tolerated.
  • Discussions that get too heated will be locked and offending comments removed.
  • Β 

    Please report posts and comments that break these rules!


    Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.

    founded 2 years ago
    MODERATORS
    you are viewing a single comment's thread
    view the rest of the comments
    [–] themoken@startrek.website 42 points 13 hours ago (3 children)

    Wayland is a sports car - modern, tailor made for performance. X is like a '99 Civic that's had the seatbelts stripped out and the airbags replaced with cameras that let all the other cars on the road see you naked.

    It's fine to prefer X, but the older it gets the more people are going to roll their eyes at you. XWayland is fine for random old stuff, but there is zero reason X should be running your whole display these days.

    Inb4 someone mentions network transparency that gimps the rest of the system or some 5000 year old app that needs to sniff events sent to every other program.

    [–] IHeartBadCode@fedia.io 9 points 12 hours ago (2 children)

    And the network transparency argument is long gone. While you can indeed network windows over the wire, most toolkits use client side rendering/decorations. So you're just sending bloated pixmaps across the wire when things like RDP , VNC, etc deal better with compression, damage to the window, etc. And anything relying or accelerated with DRI3 is just NOT network transparent.

    Most modern toolkits have moved past X11 because the X protocol was severely lacking, and there wasn't a good way as a committee to modify the protocol in an unified manner. I mean look at the entire moving Earth that it took for XFixes and Damage extensions. Toolkits wanted deep access to the underlying hardware and so they would go out of their way to work around X, because it just could not keep up.

    Tell me you never deployed remote linux desktop in an enterprise environment without telling me you never deployed remote desktop linux in an enterprise environment.

    After these decades of Wayland prosperity, I still can’t get a commercially supported remote desktop solution that works properly for a few hundred users. Why? Because on X, you could highjack the display server itself and feed that into your nice TigerVNC-server, regardless of desktop environment. Nowadays, you need to implement this in each separate compositor to do it correctly (i.e. damage tracking). Also, unlike X, Wayland generally expects a GPU in your remote desktop servers, and have you seen the prices for those lately?

    [–] themoken@startrek.website 5 points 11 hours ago

    Agreed. I was an early Wayland convert because once upon a time I started writing a WM and taking an interest in X internals... And then my face melted off like I'd opened the Ark of the Covenant.

    Things are so much simpler now.

    [–] Digit@lemmy.wtf 3 points 10 hours ago (1 children)

    Plenty life in X11 yet.

    Xlibre running around.

    Pheonix on the horizon. (Zig!)

    [–] themoken@startrek.website 11 points 10 hours ago (1 children)

    An anti-DEI fork by a wingnut and a project that isn't even half way ready to use starting from scratch in a niche language. Neither of which are capable of dealing with the fundamental problem of X, the protocol itself, without becoming something entirely different.

    ... I'm not holding my breath.

    [–] zurohki@aussie.zone 7 points 8 hours ago (1 children)

    If you deal with the fundamental problems of the protocol itself and also provide backwards compatibility... Congrats, you've just reinvented Wayland and XWayland.

    Dealing with X11's problems while still being X11, when X11 is the problem? Yeah, I wouldn't hold my breath either.

    The fundamental architectural issue with Wayland is expecting everyone to implement a compositor for a half baked, changing, protocol instead of implementing a common platform to develop on. Wayland doesn’t really exist, it’s just a few distinct developer teams playing catch-up, pretending to be compatible with each other.

    Implementing the hard part once and allowing someone to write a window manager in 100 lines of C is what X did right. Plenty of other things that are bad with X, but not that.

    [–] statelesz@slrpnk.net 2 points 12 hours ago (1 children)

    No KMag + KDE Connect remote input, no Wayland.

    [–] themoken@startrek.website 4 points 12 hours ago* (last edited 12 hours ago)

    I use KDE Connect remote input on Wayland all the time...

    KMag is broken (simply has not been updated, not like it couldn't work) but you can zoom the entire screen in KDE with super +/- is that not good enough?