That's not to say there's some non technical decisions which are making porting a lot harder *cough cough* mouse warping *cough cough*
That's not to say there's some non technical decisions which are making porting a lot harder *cough cough* mouse warping *cough cough*
You should use Wayland because it's what's supported. It's what all future Linux graphical software will be ported to. In a few years, it'll be impossible to get an X version of even a recent web browser. The best time to abandon X was 30 years ago. The second best time is now.
This is a similar situation to the people who were all screaming that you had to ditch Python 2 to upgrade to Python 3 immediately after it came out, and that if you didn't you were somehow dumb, even though they finally started to fix all of the upgrade deficiencies and regressions only with something around Python 3.5: there's a time to upgrade, and that time is never immediately upon introduction.
What people do not seem to get is that Wayland is what they wanted Xorg to be. A lot of what Wayland could not do were things they did not think it should do.
In some cases, the Wayland team has been dragged kicking to implement things. In other cases, they have stood firm and we will be leaving them behind.