What's the difference for a real user between using X11 or Wayland nowdays? I haven't found anything useful on the internet, so I'm asking you. Internet articles on the topic (and about WMs too) seem to be advertising slop since they explain anything but the real things. Also, if anyone used the XLibre fork, I would love to hear about your experience with it.

Security

When you use X11, you allow any program running on your computer to access anything on your screen and clipboard, collect your keystrokes and type. It's trivial to implement a keylogger, for example. Do not buy into the whole "no viruses on Linux" thing, it's not true and likely to become even less and less true, as desktop Linux is becoming popular.

Wayland at least tries to put some barriers in place against this.

I don't think for tue average user it really matters much. If you've got multiple screens of different sizes or refresh rates, Wayland is the way to go. If you've got multiple identical screens that you want to treat as a single big screen, X11 is perfect for that.

I recently switched and I'm happy with how it runs. Even on Nvidia.

X11 is dead don't bother with it. The same people who wrote X11 are working on Wayland because X11 became to here maintain.

X11 is still being actively maintained. It isn't an install risk or anything like that. It isn't going to add any shiny new features, but not everyone needs shiny new features. (That being said, if Wayland works for you, go ahead and use it. Just don't spread FUD, please.)

X11 has many features and some it will never have. Wayland has less features and it has compatibility issues for the ones it has. But if you need 4K or touchscreen then Wayland is the way to go. Default choice should probably be Wayland unless it doesn't support that one thing you care about.

If you use a feature complete Wayland compositor and compare it to equivalents (RIP velox), then Wayland basically offers more consistent pen and multitouch support and stuff, while being faster.

There's no 2D acceleration in Wayland and that's by design, it's made for new GPUs that don't have 2D anyway anymore. Programs either draw pixels or start up 3D.

XLibre is trying the opposite and is actually merging various 2D drivers for old and niche hardware, like ct65550 as found in the Toshiba Libretto 50ct among others. Most of these originate from distribution forks (NetBSD in this case). T2 Linux also maintains a patch to bring back lots of more ancient 2D drivers that were removed in 2012.

Every time I setup my desktop up for Wayland I always go back to X11, I find Wayland sluggish compared to X11 and don’t have the time nor energy to troubleshoot applications that had no issues working on X11.

I did not have any problems with Wayland for 6 months on Arch (personal PC for hobby projects and gaming). I also don't want to troubleshoot, it just works. Most applications are installed via flatpak.

also don't want to troubleshoot, it just works. Most applications are installed via flatpak.

I’m not surprised Flatpaks work with Wayland without issue, however Flatpaks containerize the application which is something I don’t want to do for everything I download as it adds extra overhead for something that could’ve just been built and installed as a native package (.deb, .rpm).

To each their own though.

Yes. This is still an important point, you make!

Wayland has been the default for awhile, but open source software is maintained by volunteers.

Until each specific package has been updated by the original developers, it may not work well on Wayland.

So, for now, there's also a trade-off:

  • Love running brand new shiny software, better use Wayland. Wayland has been the usual default for awhile, so new code is unlikely to get tested for speed and smoothness on X11.
  • Have a whole set of preferred older good enough software that hasn't been updated lately? Consider using X11 for a bit longer until someone who loves those tools updates them.

X11 is still server-first and needs workarounds to run locally (like startx, sx), while Wayland can just be run. Unlike X, it isolates every processes access to other windows, but with slow adoption of protocols for things like screen-sharing, video conferences, accessibility tools. The tooling is not yet there imo.

That's the main difference nowadays. Some people have issues with tearing or wrong-monitor with either of them.

Honestly, Wayland vs. X (and Flatpak) fit this perfectly:

X11 is stable and maintained but not getting new features. It will generally work well for most people but over time it will and is drifting to obsolesence.

Wayland has some flaws but is not basically stable and feature rich enough for most people to use. It is not a complete drop in for X11 and won't necessairly ever will be but for the vast majorory of desktop users it is.

The problem with Wayland is that there are still issues for people with graphics drivers. Nvidia in particular has had serious issues with it although they are improving.

I personally still use X11 with my KDE set up because i still have problems woth Wayland. Thwyre not as bad as they were but its still not quite stable above for me.

Some things still don't work on Wayland.
(Like screen sharing with Anydesk, as an example I ran into yesterday)
But at this point, I just replace the thing that still requires X11 with an alternative, or find a different solution.
X11 is dead tech. Wayland has its own issues, but it's better than X11 in almost every way now, actively maintained, and it's the current standard.

no screensharing seems to work, at least none of those i tested, not even jitsi meet. i get the point of "being maintained". but but what does it actually do better?

Test better.

  • Discord works
  • Teams works
  • OBS works
  • Sunshine works like a charm
  • Built-in VNC/RDP servers work
  • I think zoom also works

Of course you can expect things with names like "Xultra-Xold-Xscreen-Xsharing-Xtool-11" to not work. Trying any of those and complaining it doesn't work is just disingenuous and facetious.

Edit: I forgot you had a real question after the misinformation. Here's some things Wayland does better

  • It supports HDR
  • It doesn't tear
  • It's by design more efficient
  • It's more secure
  • It actually support track pads with kinetic scrolling (if you think kinetic scrolling works on X11 it means you don't know how it works)
  • To crash the screensaver you need to crash the whole desktop, which means you don't get unauthorized access to it
  • It actually supports multiple monitor (with different resolutions, different scales and different refresh rates)
  • They just merged actual support for multiple GPUs (xorg doesn't have that)
  • It supports explicit sync (xorg supports just enough to run inside Wayland)
  • It's supported by Nvidia GPUs (for X11 you need to use Nvidia's closed source bespoke implementation of xorg)

But it's just to name a few, you know...

Yup. Zoom works, so does google meet.

What you listed is heavily dependent on compositor. Screensharing for my wayland setup meant setting up 6 deamons that talk among eachother. It's not difficult once set up, but still...

As some general advice: If you don't know the specifics, just go with your Linux distribution's defaults. They probably have this figured out for you. Wayland is the more modern approach. We had a long transitioning period and some things didn't work for a while or were missing. I'd say it's ready by now. And if your distro maintainers also think it's time to supersede the old X server, it probably is.

We had a long transitioning period and some things didn’t work for a while or were missing. I’d say it’s ready by now.

Do things like xdotool and xinput still work?

Uinput and libinput are the proper tools and they both work.

Also, the keyboard configuration is done with xkb

There's ydotool

The x is the clue in those programs. They are tools to interact with x11. There will be tools to interact with Wayland, or there will be hacks to get x programs to sort of work with Wayland.

There will be tools to interact with Wayland

I don't really like the hypothetical sound of this.

xdotool is essential for keeping some of my basic hardware usable.

(Yeah ... more and more, I think I'm going to be a very late adopter of Wayland. I was planning on Debian Stable for my next install anyway...)

xdotool is essential for keeping some of my basic hardware usable.

That's a good sign that you may not want to upgrade to Wayland on that hardware.

Which is on Wayland

Nope. But you can find ydotool 🙄

I mean the ELI5 for the uninitiated is that X11 is older, and Wayland was made as the successor to X11. It aims to address issues that a lot of people had with X11. X11 is not in active development whereas Wayland is, and for support for modern tech, it'll be added to Wayland but not X11. These days I'd advise to go with Wayland unless you either have hardware that doesn't place nicely with it or you have a specific use-case for X11, i.e. Wayland unless you have a reason not to. Although most "beginner" distros choose for you without prompting you to pick, in which case go with the default (it's probably Wayland anyway).

If you mean to explain the debate, basically some people have particular things they want to do, or they want to do something a certain way, and it's not supported by Wayland, usually by design due to things like security concerns or philosophical differences with X11. X11 will continue to work for a long time but it's not getting new features, so if these issues are a concern with you, you could stick to X11 for the foreseeable future.

The average user is not supposed to notice a difference (apart from maybe QoL differences like performance, screen tearing, etc)—that's the goal of both projects. It should just display your desktop.

one thing i noticed in trying both is x11 using more cpu in the same scenario (playing a youtube video, same resolution) and even the DP adapter i am using getting warmer when on x11 compared to wayland. in this scenario the difference wasn't much despite being roughly double (~2.5W compared to ~4.5W in x11). idk how that scales in other scenarios.

Wayland is more secure than x11 by design and more concise in scope. Notably it supports contemporary display technologies like display independent scaling, VRR, colour space (HDR) and several others.

Wayland is made by the x11 people.

By real user, do you mean a nontechnical user? If that's the case, the display server isn't a choice to be made by such user, but by the distro maintainers. Most people won't notice the difference, because it's mostly stuff that happens under the hood.

Honestly, on a running system with average hardware, the average user won't notice any difference. Depending on your de/wm of choice on x11, you may have to swap to something similar but different, but there it. Depending on what you used, something will require different solutions, like screenshots, but 90+% of stuff, there is no difference.

I'd like to chime in on the "average hardware" claim.

The idea that Wayland is more demanding to run than X11 is a misconception.

Mutter (Gnome's compositor) and kwin (KDE's compositor) are more demanding than xorg plus a simple window manager. Usually that's what people used to compare when they said that Wayland is demanding, and now they just keep repeating it.

In actuality, the Wayland protocol is more efficient by nature. So a light Wayland compositor (e.g. labwc) will run better on limited hardware, than a light X11 window manager.

Tho, Wayland requires proper EGL support, which you might not have on some old exotic hardware (e.g. a Tegra 2/3/4 tablet).

The example I usually make is:

  • Dig up an old intel atom netbook (it's old and
  • Try using regular lxqt on x11
  • Now try lxqt on labwc
  • See which one you'd rather use

Is it even a debate at this point? x11 is on it's way out and wayland transition is pretty much complete within the gnu/linux ecosystem. Vast majority of distros and desktop environments ship with wayland as the default and keep developing with wayland in mind, with holdouts like debian and mint that still use x11, I think. X11 is basically dinosaur software for legacy. Vast majority of end users will just take what is the default and that is Wayland and they don't even notice.

I use Debian GNOME and Wayland is the default now, with GNOME on Xorg as an optional session in the login manager.

On most distros Wayland is trouble free and x11 is a thing of the past. X11 made some things simpler like screen share with somebody , but Linux is growing large enough that Wayland (that is secure) is the best choice. You don't want your x11 screen duplicated on a malware attackers screen etc.

One thing that's annoying in Wayland is new window placement where app can't control it at all*. Wayland would place it on a screen it wants. This gets hugely annoying when you have more than one monitor and/or virtual desktops and you'd want to restore billion of browser windows, for example.

  • A solution is being worked on, luckily
  • for most people, use whatever your distro ships with and installs for you
  • choosing desktop environments still starts heated discussions – high end, it’s a choice between Gnome and KDE – mid-tier has Xfce, LXQt, Mate, Cinnamon, and more – limited hardware go for IceWM, JWM, FLWM, or similar – want to get your hands dirty? go for a tiling window manager
  • X11 is (effectively) abandonware at this point – it’s still getting security patches, but the devs left and started Wayland 17-ish years ago
  • XLibre is more political than technical – and I’ll leave it at that

Why is XLibre political?

Mainly their readme being fully magat-pilled, talking about DEI and whatnot. They also waste time on things like renaming functions to own the libs. It's not a project that i put any trust into and i'd rather use plain X11 if i had to go back.

If we ignore the deeply disturbing political views of the Creator the entire project is meant to be a statement. There's a conspiracy theory that there was a grand plot to kill x11 by red hat and xlibre is built upon the idea that red hat was holding it back. This completely ignores the real issues that the codebase was pure spaghetti.

I heard that XLibre developers are working on cleaning the codebase. And I strongly believe we still need X11 at least until Wayland is polished enough, which still seems untrue even in 2026. The concerns about Red Hat are not conspiracy, a commercial corporation controlling important parts of Linux ecosystem is a serious threat, so having an alternative is never bad. Linux won't have a future if everyone just uses Red Hat approved solutions.

https://github.com/X11Libre/xserver/pull/56

Here is the x11libre dev not understanding what the ^ operand does in C. Would you trust running this person's code as a display server?

Sure. No one expects anyone to know everything from the start, and people improve with time. But this was metux's understanding of C when he forked off xorg thinking he could do better than freedesktop.

You know that "until Wayland is polished enough" is at least a year ago for the overwhelming majority of people, right?

A year ago I got a new PC, installed Ubuntu 24.04 which defaults to Wayland, and installed discord. Push to talk wouldn't work unless discord had mouse focus. I spent a few hours researching and trying different things before switching to X11 where it just immediately works.

Tell me more about how polished Wayland is.

That is a feature. Allowing arbitrary programs to read any key press is how you get keyloggers.

Wayland has a protocol to request reading keys out of focus (which will ask the user for permission, as opposed to just read it like on xorg).

If the program was running in xwayland (which it probably was) of course it won't use that protocol, and will just try to read it X11 style.

In some DEs (KDE) you can select if X11 apps are allowed to read keys.

"I switched to X11 and it immediately works". I'll give you another tip: if you run chmod 777 -R / the file manager stops pestering about permissions and it immediately works.

Yes, you clearly understand the problem, thank you. If there's a problem with filesystem permissions you can use tools like chmod, chown, and setfacl to fix them in a variety of ways.

How do you fix a wayland session if your app doesn't properly support GlobalShortcuts? Where's the chmod 777 equivalent that lets the user say "I know this means this can spy on everything I do but I'd prefer this work today instead of waiting on a bug fix." Without something like this, the entire desktop ecosystem needs to mature before you can call Wayland "polished."

Fam, if I may, I'll be a bit abrasive and blunt for the sake of brevity. So, without further ado.

Ubuntu 24.04

(I'll assume this is on GNOME.) First of, in terms of Wayland development, that build is from the Bronze Age. The associated issue tracker has been closed since last year, even if you don't like the solution GNOME has come up with. Which, gets us to the second point; please don't blame the Wayland ecosystem as a whole whenever you find a fault within a Wayland compositor. If, instead, you would have been on KDE Plasma back then, you'd have found that PTT was supported. Even if it was basically a hack for the sake of UX. Thankfully, KDE Plasma has recently merged a proper implementation that's slated for its 6.7 release.

I'll grant you that the Wayland ecosystem hasn't fully matured yet. But it's undeniable that it already provides a better experience than its predecessor for the vast majority of users.

Fair points all around. I wasn't thinking about version locks for the LTS releases when I posted, and it looks like I wouldn't have had an issue on GNOME 48.

I think the maturity of the ecosystem has a larger impact on user experience than you're giving it credit for. I understand wayland and the rest of the desktop ecosystem will someday (maybe today for those living on the bleeding edge) provide meaningful benefits over X11 without drawbacks. I'll welcome it when it does, but in the meantime I don't want to deal with troubleshooting my discord keybinds, or figuring out why Spotify has a weird window border. I want my desktop environment to Just Work™. It's immaterial if the fault lies with wayland, GNOME, or Canonical for shipping wayland as a default while GNOME support still needed improvements. The end result is that as a user the only way to easily fix my problem is to use an X11 session instead of wayland, which makes wayland look like the problem.

Two things, one as previously mentioned the codebase is a mess and even the best developers working on x11 tend to introduce regressions (the xlibre dev isn't so this is amplified). Second it absolutely is a conspiracy because red hat did everything in the power to save x11 until eventually they just kept using it (tbh it needed to be replaced two decades ago). As for your last point linux won't have a future if its aggressively held back by an army of enthusiasts who demand things never change and fragmented until software support is non-existent.

The Linux ecosystem would whither and die without the likes of Red Hat.

I'm a bit surprised you didn't find much searching the web, because this is one of the most hot topics in Linux and everyone has an opinion and discussions are endless.

I use Wayland for years by now and it improved vastly during that time. One of the advantages over X11 I appreciate is the better handling of multiple monitors, with different resolution, refreshrate and VRR in effect. This was simply not possible in X11 in this form. I like its more secure by design, in relation to keyboard input. X11 can read all keyboard input by any application at any time. Wayland works different here, but for the time being I enabled X11 compatibility for this in KDE, until a all applications support Wayland fully.

Think twice before abandoning X11. Wayland breaks everything! is more of an anti Wayland posting, but its good to have a view from all angles. So I post it here.

Have in mind that Wayland improved in recent years drastically. Searching the web is either full of Ai nonsense or old content about the old state of Wayland. Also it depends which desktop environment you are using, because some are better at Wayland than others; notably KDE is on the front regarding Wayland. So even if some Wayland features are already developed, does not mean that all desktop environments supports them already.

I’m a bit surprised you didn’t find much searching the web, because this is one of the most hot topics in Linux and everyone has an opinion and discussions are endless.

it's 2026. OP probably only found useless AI slop articles after a couple searches before getting discouraged and asking here

You can't imagine how sad your comment makes me feel.

I realized this later in my reply too and answered that to myself. Should have read it in full before pressing the reply button, as my thoughts changed a bit during a research phase. I realized its Ai bullshit all over the place when doing research to give links.

Jesus, there's so much FUD in that gist. A lot of information out of date and emotional tone to the brim. Makes you wonder who's putting that much time and effort to support an outdated system like x11 and what they gain from that.

The reality is that the main desktop managers, and by extension the most popular distros are abandoning x11, so that's just a silly hill to die on.

Think twice before abandoning X11. Wayland breaks everything! is more of an anti Wayland posting, but its good to have a view from all angles. So I post it here.

I like how you slightly poison the well there ("more of an anti Wayland posting) rather than pointing out that Wayland has very real problems even after >10 years of development.

And X11 does not have problems? Atleast post the issues you still have today(!) with wayland so people can make an informed opinion.

"I like pancakes"

Internet morons: "Oh so you hate waffles and anyone who eats them???"

You accuse me of poison? What nonsense is this? The author is anti Wayland and the entire post is about reasoning why you should not use Wayland. This is anti Wayland, not my opinion, no poisoning, nothing. I don't agree with that person but still included it here, so we can see others perspectives too. I did not include any opinion or judge of me about that article, so nobody is poisoned by my opinion before reading it.

rather than pointing out that Wayland has very real problems even after >10 years of development.

Why don't you do that? As you clearly know more than me.

The author is anti Wayland

The authors' point of view does not matter. You've poisoned the well by presenting the data collected as potentially "tainted" by a bias that, even if true, does not change the data presented.

So yes - clearly and very obviously poisoning the well. Textbook really.

Why don't you do that?

The link you provided actually did that. But they are "anti-wayland"...

Edit: and I'll push back hard on the "anti-wayland" language as well. This is propaganda-style speech. People can "not like things" and disagree. But labeling somebody "anti-x" diminishes their opinions and ideas.

Wayland breaks everything is right in the title. Did you even look into the link before you accuse ME of propaganda? I did not poison the well and left my opinion out. The article IS anti Wayland, and that is not my opinion and does not reflect my opinion. You should stop right there.

Edit:

you: rather than pointing out that Wayland has very real problems even after >10 years of development.

me: Why don’t you do that?

you: The link you provided actually did that. But they are “anti-wayland”…

But you expect ME to do it, when I ask you to do the same?

Wayland breaks everything is right in the title. Did you even look into the link before you accuse ME of propaganda? I did not poison the well and left my opinion out. The article IS anti Wayland, and that is not my opinion and does not reflect my opinion. You should stop right there.

You're just anti-X11.

You just attack me personally the whole time with wrong accusations, instead bringing arguments for or against Wayland and X11.

Edit: You call me doing propaganda, you call me poisoning the opinions of others, you call me anti X11. Just because I call the article Anti Wayland. That's it, that is your basis. Even though I provided that link to have a different view in the mix our discussions too. I ask you, would you not consider the article I linked being Anti Wayland? Strange because it ONLY speaks about its problems (some not even true anymore), but not about its strengths. Also you call me anti-X11 (to me personally), but you say its propaganda speech if I say Anti Wayland (about the article).

You just attack me personally the whole time with wrong accusations, instead bringing arguments for or against Wayland and X11.

I very clearly attacked your argument (not you) as "Poisoning the Well". Sounds like you're not familiar with logical fallacies, I highly recommend reading up on them.

you call me anti X11

Yes - that was me doing to you what you did to the author to show by example. You took that as an insult which is why I say calling the author of that article "anti-wayland" is well-poisoning. You've set the tone that the article is not to be taken seriously because of a perceived bias on the part of the author. You "besmirched" their reputation to, by association, attack the argument. This is practically the definition of Poisoning the Well.

Just because I call the article Anti Wayland. That’s it, that is your basis.

Yes - that was the fallacy. The "well-poisoning" if you will. If you simply said "Here is an article that points out some of the problems with Wayland" or something to that effect I wouldn't have taken any issue.

As an average user, I notice input issues, multi-monitor issues and incorrect animations in Wayland. X11 just works fine. But somehow pointing out problems with Wayland always gets you downvoted because it's "newer and more secure".

Multi-monitor issues surprises me, considering multi-monitor support is kind of a sellingpoint for wayland. I don't think animations being incorrect has anything to do with wayland itself though, it's up to the individual compositors to handle that.

Specifically, it's windows opening in the wrong screen. In some full-screen Wine games it means games crash when you move them.

And for animations, if I use touchpad 3-finger touch to switch desktops, the animation is reversed.

But somehow pointing out problems with Wayland always gets you downvoted because it’s “newer and more secure”.

That's not the reason why he got downvotes. In fact, he didn't even mention what problems Wayland has. Contrary to him, I even posted a huge link with massive listings why Wayland sucks. I also pointed out 2 problems in my comment he is replying to.

On my 2014 PC I'm using Fedora 44 with KDE, which defaults to Wayland: not problems whatsoever, but some applications say "Wayland support is experimental, beware".

I switched to X11 after a suggestion to debug some issues with a game. The issues was not fixed, all the other applications I've tried are still working flawlessly. PLUS the KDE night light feature is working (was not in Wayland). So I stayed with X11.

On my wife MacBook (2015) I installed Kinoite, defaults to Wayland. Everything works, but Rustdesk renders VERY small. I have not tried X11 on that, and will not try it.

Try both with all your applications and setups and choose the smoother experience. Make security a secondary priority: if it was the first you have less attack surface sticking to terminal only.

Wait, you installed Linux on a MacBook?

You always could do that before the M chips

Yes: it was the only way to update the software inside. It was so old some pages refused to load, and was really slow. It was a painless and quick procedure and it has been working better than ever since then: decent hardware with (now) very good software.

This is... decent

It depends heavily on your hardware and workflow.

Wayland can be a great experience and I personally enjoy how smooth it feels, but I acknowledge that many people run into some problems.

I personally haven't really seen much difference between the two except Wayland eating more CPU and being rather tedious for hybrid (Ryzen/Nvidia) setups (still haven't resolved it crashing when I change TTY). I'd personally say stick to whatever default your desktop environment runs on..XWayland helps with the whole compatibility concerns at least.

Just my experience though, yours could be different depending on your machine and general setup

Wayland is (part of) the modern solution to the problem that was previously tackled by X11. As such, it comes with improved security (read: keyloggers no longer have a field day) and features (read: HDR, VRR and no screen tearing) that one might expect in 2026. Furthermore, it breaks up the monolith of X11 and thus adheres better to the Unix Philosophy^[That is; Do one thing and do it well.] (if that happens to be something you care about). Finally, Wayland has basically come (as part of the plan) to replace X11. So, it will continue to improve as a platform while X11 will remain stagnant.

In the current landscape in which Wayland has (finally) fulfilled (most of) its promises, X11's lifeline are the edge cases in which (for a myriad of different reasons) the Wayland ecosystem hasn't reached full feature-parity yet. And Wayland's trajectory would suggest that it's only a matter of time until those have been ironed out as well.

TL;DR: Use Wayland. Most of the ecosystem has already adopted it and what remains is actively in the process of doing so.

Wayland has basically come (as part of the plan) to replace X11

As part of whose plan?

The very same people that actually worked on X11. Wayland is basically X12.

The project recognized that a complete redesign was required and they followed through.

The X11 developers

As someone who has used X11 and Wayland, it doesn't matter for the typical user. If you, like me, have a penchant for some smaller desktop environments like XFCE or window managers, you will be stuck with X11, but many are already working on porting to Wayland.

Couple edge cases for gaming, namely screen tearing on some X11 configurations and certain Nvidia hardware running into issues on Wayland. For multi-monitor or high DPI users, Wayland handles per-monitor DPI and fractional scaling far better than X11. Maybe a couple more edge use cases for remoting into the desktop, but Wayland support is also improving quickly on that end. In any case, Wayland is by design more secure than X11.

I thought I’d never have to care about X11 or Wayland if I was a typical user. I thought it was just a debate for really passionate Linux user.

I turned out to be false since the reason I had bad playback on my HTPC, was the fact that Wayland was preventing the refresh rate of my TV to be adjusted to the content.

Switching to a distro using X11 solved the issue and apparently Wayland doesn’t plan on changing anything about this issue.

Wayland doesn’t plan on changing anything about this issue.

This seems to be a common pattern with the Wayland team. They seem very focused on some technical ideology for how "things should work" to the point of ignoring or dismissing real-world issues.

Perhaps in another 20 years they'll get around to addressing it.

Waylad is technically a better idea, the progression of X11, more secure and should be faster and smoother when it's ready...

But I run into so many incompatabilities still and often janky support via xWayland that I really don't think Wayland is ready to be the default just yet.

It will be, I'm sure, but for now I spend more time fighting it than I do using it. A bit of snazz in KDE and Waydroid seem to be the only things that actually need it, for me, and so many legacy things just nope right out and crash without going back to x by force.

There is a workaround to run Waydroid on X11, so you can still run it even if Wayland doesn't support your window manager.

the progression of X11

Unless they reach feature parity, it's a fork, not a progression.

It's not a fork though?

You can run either. The truth is depending on what you want to do, what hardware you running, and software versions you have available, your experience will be very different.

Personally I run X11 because I'm used to it. It's extremely stable and the failure points are well known.

The waylandism design really bothers me, and so does the attitude of waylandists. Throwing stuff that works away for no reason, chasing some sort of Android trash ecosystem dream that's never going to happen.

Whatever man, you're taking xgamma away from me over my dead body. cocks shotgun. Come and get it.

I think x11 is for older computers , or the ones that are not that powerful , while wayland is for capable computers . I am not sure though so someone please confirm! :)

Edit: So many downvots :)

You just came here to guess? Or why did you post this knowing nothing on the topic?

midwest.social

Rules

  1. No porn.
  2. No bigotry, hate speech.
  3. No ads / spamming.
  4. No conspiracies / QAnon / antivaxx sentiment
  5. No zionists
  6. No fascists

Chat Room

Matrix chat room: https://matrix.to/#/#midwestsociallemmy:matrix.org

Communities

Communities from our friends:

Donations

LiberaPay link: https://liberapay.com/seahorse