Both are display servers which is software that allows programs to write to the screen. X is older and was created back in 1984 at MIT and Wayland is a much newer protocol that is designed to work better on newer (post 90’s) hardware.

The biggest difference is that Wayland basicly allows your desktop direct access to the screen and X has a server that runs and allows your desktop to connect to it. X was originally designed to run remotely as back in the day there was one big commuter that many people connected to.

If this is all very confusing you probably should just stick to your distros defaults. Most of the time you don’t need to care.

From a user perspective, Wayland is smoother and looks nicer.

xorg is a old implementation of x11, which is basically abandon-ware right now. No one is adding feature to it, testing it, or fixing security vulnerabilities. It also lack some common-sense security feature: for example every program can get every input (keyboard and cursor location) without root, so a key logger is trivial to implement in xorg.

Wayland is newer, with more features (reasonable multi-monitor support, one-to-one gestures, etc). But many application framework and hardware have poor support for it, because it is slightly newer (developed on 2008, so not that new any more). Notably, electron and nvidia are typically the worst offender, like everything on linux, but both has come a long way.

I have wayland on my laptop, since one-to-one gesture is a must for me, and I present quite often using that laptop. My desktop is on xorg, since I have a nvidia GPU and use quite a lot of electron app.

Desktop Linux is in its never-ending process of replacing old displaying system with new one. The process is long and not really transparent, because the two displaying systems were designed in completely different times for different hardware and with different security concerns in mind, therefore the X11 clients (all the software that was ever made or ported to Linux) are very much incompatible with Wayland. For backwards compatibility there’s Xwayland, which provides full blown Xorg server running on top of Wayland compositor with all the things X11 app requires. Until now, Firefox, even though had its Wayland backend as WIP feature (possible to activate with environment variable MOZ_ENABLE_WAYLAND=1) it defaulted to Xwayland on Wayland sessions. It now uses native Wayland backend by default providing better efficiency, DPI scaling, touchpad gestures etc

I’m not an erudite so feel free to correct me c:

Wayland is a new implementation on how your system draws windows and components in your computer (I’m not sure if it’s responsible for the content) and it tries a different way to do it compared with xorg.

Xorg is the old implementation, and it has been patched to support most of the new features, and Wayland is trying to get the same features xorg has and some extras.

As a Linux user I have noted that sharing screen is more private in Wayland, also I think multi monitor refresh rate was a problem in xorg. One common issue with Wayland is the GPU compatibility, as far as I know Wayland runs better in AMD GPU I think is because of Mesa integration.

I’m not an expert on the matter so have a Wikipedia link.

Thanks for all the responses. All of them have been so helpful. What I’m getting is that at this moment Wayland can be seen as a successor to Xorg?

I wouldn’t worry about it too much; there’s not really anything you need to do as a user anyway.

Xorg and Wayland are graphics systems. You may have seen a command line during boot with tons of text scrolling past, that’s all you get without either Xorg or some alternative running.

Xorg runs on X11, which was designed a long time ago during the mainframe era of computers. It used to be the standard for all GUIs on Linux, BSD, and other Unixlikes for ages.

However, modern computers are nothing like the computers X11 was originally based on, and X11 started showing shortcomings. So, years ago people working on Linux decided it was time to design a new system, one that’s designed around our modern computers and operating systems. That new system is Wayland, through Ubuntu sported their own Mir for a while too.

Wayland was designed not to be a network protocol (though you can still run applications on remote computers if you wish). It also has a bunch of security benefits, like “not every application can read your key strokes, copy your password, or record your screen without you noticing”.

This new system doesn’t have the benefit of multiple decades of hard work behind it. As you may imagine, this also broke applications for a while. There’s a tool called XWayland that can run X11 applications on Wayland, so most programs just work, but things like screen recording are severely limited under thst system.

On the other hand, if you’re on a laptop, Linux can now finally reliably use touch pad gestures with more than two fingers through Wayland. You could write scripts and tools to fake them before, but they’re actually part of the UI nlw.

Wayland does have APIs for almost everything now, but not all applications have been updated to use those APIs. For example, Zoom didn’t wait for the screen recording API to be standardised, so it implemented screen sharing under Wayland as “take a thousand screenshots”. Some programs work by listening for keyboard hotkeys (basically processing every key and checking if it’s their special hotkey) but that’s no longer supported unless the program has focus.

There were also issues with drivers (well, almost exclusively Nvidia) but those have mostly been solved. It’s not for everyone yet, but there’s no reason not to try Wayland if you don’t have a full Linux setup already, anymore.

As with any big change to the Linux ecosystem (systemd, anyone?) there’s a lot of fighting between people who want the shiny, better new thing, and people who liked the way things were before. Both sides have good arguments. Big parties in the Linux world, like Gnome and KDE, are moving towards a Wayland-only desktop. At the moment you can run Gnome and KDE on either, but that’ll be harder in the future. Other GUIs, like XFCE, are heavily geared towards X11, and it may take years before you can even run those on Wayland. Some, like i3, have replacements (Sway) that do almost the same thing.

Interestingly, hardware vendors also seem to go with Wayland for their custom Linux projects. For example, the Tizen watches Samsung used to sell run Wayland. The Steam Deck runs Wayland in game mode, using a purpose built Wayland compositor as a GUI, but X11 for desktop mode.

In practice, you shouldn’t need to worry about things too much right now. Some programs will not work on Wayland, others will not work on X11. Some games run a few fps faster on Wayland, others run faster on X11, but the differences aren’t huge. If both Xorg and Wayland are supported in your distro, you can switch between the two using a button on the login screen.

As for Firefox: Firefox has had native Wayland support for a while. It was already capable of using all the Wayland APIs and protocols at least a year ago. However, by default, it ran through XWayland, to remain as compatible as possible, while Wayland was still being tested. Now, with the upcoming release, Firefox goes native.

For Xorg users, nothing will change. For Wayland users with touchpads or touch screens, gestures like pinch to zoom will be smoother and there will be more of them. The only difference is that you don’t need to stuff MOZ_ENABLE_WAYLAND=1 in a script somewhere to activate the new capabilities on Wayland.

Xorg = Massive screen tearing

Wayland = No screen tearing

Xorg = Nvidia friendly

Wayland = Fuck you nvidia!

For a user: In Wayland programs are supposed to draw their own title bar. Java aplications and old applications must use a backwards compatibility layer that can cause flicker and bad font rendering. The terminology is different (compositor = window manager). Some niche new programs may only run on Wayland. Wayland hasn’t been adopted by BSD (AFAIK).

For a programners: Wayland has more modern, tidy code, but not all toolkits support it natively and few are easy. If you code exclusively for Wayland, a lot of users won’t use your program at the moment.

how many people know what wayland is? pls use this comment as a poll ;)

deleted by creator

Yes, you should.

Is it though https://gitlab.freedesktop.org/mstoeckl/waypipe