We'll wait until it's not "what if".

11 members found this post helpful.

This presentation on Wayland and X is pretty good imo. I think it sounds like Wayland is a good idea and the core design of X is outdated and hard to work with.

I, personally don't understand the situation enough to really care. X11 works for me at the moment, but it sounds like Wayland is the future. If Wayland becomes stable enough to be included in Slackware, I'll start using it. I'll trust Pat's discretion here.

Or what if both fall flat as experimental software pushed by Canonical, and Xorg shines as it always has.

2 members found this post helpful.

Ill second that.

If it's really better than Xorg. I voted for third variant.

Fourthed.
What he said, as well.

Not before it is included by the dev team

I'm certainly intrigued by wayland...

Seems to me we are going a sort of systemd route.

Xorg does for me and if it ain't broke etc.

2 members found this post helpful.

I will definitely give it a try once there are other WMs/DEs than only Enlightenment and Weston that can run on it natively.

Some clarifications:
Due to the design of Wayland, running X applications (read: applications that either speak directly with X or use an older, not ported toolkit) in a Wayland compositor should be faster than running them on Xorg. First tests with 2D X applications on Weston support that.

Benefits from Wayland, at least the ones I know:
- Every rendered frame is perfect, no tearing in videos.
- Faster by design
- Security issues of X that can't be resolved due to design are fixed in Wayland.

Regarding your programs, any application that is directly dependent on a Xserver or uses a toolkit that does not support Wayland (for example fltk, Qt<5.2, GTK<3.10?) will be able to run using XWayland.

Of course you will. How should changing the display server change the need for hardware drivers?
Wayland is developed because the Xorg developers see problems in the X protocol and the Xorg implementation that they can't solve without breaking compatibility. Therefore they invented Wayland, backports to X won't happen.

Wayland is neither developed nor pushed by Canonical. Also, it is the Xorg developers themselves who don't think that Xorg shines, which is the reason for them to work on Wayland.
This has nothing to do with systemd at all, neither the way it is developed, nor is there any forcibly pushing into distros. Mentioning systemd in totally unrelated threads in the Slackware forum is, IMHO, only a way to derail the thread.
At least the Xorg security model is broken. According to the Xorg developers that is not the only thing that is.

Of course when or if ever it will be part of Slackware is up to PV and extended testing is necessary before even thinking about it, but to me it seems that the development model of Slackware and Wayland have at least some things in common. I would like to see it in Slackware in the future, if it works as intended.

12 members found this post helpful.

As others mentioned above, I'll leave the decision to the people who know what they are talking about. I have way too little knowledge about Xorg/Wayland to make a truly informed choice. While I could do research and decide for myself, I don't really need to. I'm happy with the X server that Slackware ships with and if at some point Pat will make a decision to switch I'll trust his judgement. Long gone are the times when I 'had' to make any fundamental changes to linux to make it work for me (eg. audio/video/wifi, etc). Slackware works well for me as it ships.

1 members found this post helpful.

Therein lies the key...

Well, it seems to benefit the Raspberry Pi at least
http://www.raspberrypi.org/archives/4053

If it means a smoother desktop on my PC as well and it doesn't crash all the time, sure I'll use it.

I forget where I read it but some place had a good article on wayland it might have been phoronix or toms hardware.
problem with Xorg is it has bugs some 20 years old and is dependent upon them when programmers go to do something it is not working out well. A number of the wayland programmers are former Xorg programmers.

I hope Wayland gets programmed well and catches up to what Xorg is doing though hope Wayland faster, more efficient and stable.

probably be forever for Pat to include in Slackware but thats not such a bad thing imo, Pat keeps Slackware one of the nicest distro's.

If you want to know what makes wayland different than X.
Please read this post on freedesktop.org: http://wayland.freedesktop.org/architecture.html

According to press releases of freedesktop
Wayland reached stable 8 months ago. with their version 1.0
From that point the DE's (KDE/GNOME/Enlightment) started to announce that they would port their DE to wayland.

Looking at the development cycle of the 2 bigger DE's (KDE and GNOME), the following possible assumptions can be made.

KDE (QT5 - Plasma framework 2) is ported to Wayland, with backwards compatibility of X.
so when KDE 5.0 comes out it should work on Wayland.

GNOME, 3.10 should have a working Wayland port, but X is still the primary Display Server.
with 3.12 Wayland should become the primary Display Server with fallback to XWayland for those applications that are not ported to Wayland.

Both KDE 5 and GNOME 3.12 are scheduled for 2nd quarter 2014.
So we can make a possible assumption that not before that time Slackware will have a stable release with Wayland (maybe in their -current)

The bug list is relative small compared to X. (the bugs that could not be solved in X are dealt with directly during development of Wayland)

2 members found this post helpful.