I'm not specifically happy with Wayland, I don't care much actually. And I don't have any animosity against X neither. X is an iconic project, and inspiring too

I'm not specifically happy with Wayland, I don't care much actually. And I don't have any animosity against X neither. X is an iconic project, and inspiring too. I also spent almost 20 years using it. But it is dying. Its design doesn't correspond to the way things work anymore. It is a nightmare to maintain because its (old) code is incredibly complex, because it is full of features, and these features need to be kept for backward compatibility but aren't used much anymore. Modern toolkits actually bypass its features when they can: instead of drawing using X directives, they stream huge pictures they draw themselves. X wasn't designed like this, but it was getting in the way so this was shoehorned into it. It's now common to have two screens with different dpis, which X doesn't handle. With X, drivers are provided with X, but it is now normal to have the drivers in the kernel instead. The X developers went away to design and develop Wayland to start from a clean slate, with all the insight gathered all these years. Drivers and apps are now developed against Wayland and are less and less tested on X. Things are going to startup breaking, I suspect librairies will startup removing X support at dôme point, etc. X is not an alternative to Wayland. It is its past. I don't wish X to die at all. I have no feelings here. But that's what's happening. I don't mind someone using X knowing all this. But we are commenting on a guide directed towards newcomers. Because all these reasons, making them use X is bad advice. If you have a working install using X, there's no urge to switch. Don't fix it if it ain't broken. It might even be clever to follow the upgrade path of your distro if you didn't customize anything. Apart from that, I don't see any reason today to use X instead of Wayland unless specifically something doesn't work. And if it is the case, I hope you reported the issue, because one day you might be forced to switch and if the bug is still there, you will have to live with it. We are not in a situation where we have two competing alternatives between which you can freely chose. Both involve the same developers, and one of them is considered obsolete and isn't developed anymore. It's not that we are Wayland fans (at least I'm not). It's just that Wayland is all we have going forward.