XLibre support for future Budige desktops.

[32bitx64bit]

I know x11 is supposed to be removed, but XLibre has come out recently, which its goals are to modernize X11, make it more secure w/o feature compromise, and general code cleanups / performance improvements.

I'd hope y'all reconsider dropping X11. As XLibre has a pretty good feature, already getting 2.5k stars at the time of writing in the github repo, and its only been like a week.

(XLibre is also a dropin replacement for Xorg.)

Wayland also doesn't have the feature set that most users would like.
Such as Global hot keys, use of third party screenshot utilities like KSnip, and just other general annoyances that makes using Wayland not very practice.

Of course I fully get wanting to wait to see where XLibre goes, but its good to open a discussion, as I plan on using Budgie when when Budgie 11 comes out. At least if it supports XLibre, or Wayland gets on with feature parity with X11.

Anyways, love to hear y'alls thoughts, no real harm in keeping a X11 session around, especially given the new developments and revitalized interest in Xorg due to XLibre.

[fossfreedom]

Budgie 10.10 will be wayland only. All of the x11 code has been removed from the main branch.
Maintaining both is too large a job for the small number of contributors hence the decision over a year ago when x11 depreciation was announced to switch to the then only viable candidate.

[32bitx64bit]

Hope this is reconsidered if XLibre becomes a popular successor for Wayland.
Wayland is not great for the user, especially people who have disabilities. Or just don't like even further big tech involvement in their OS, such as systemd and wayland / xorg.
And wayland doesn't (And will probably never) cover all common use cases, especially for gaming like auto clickers, macro software like AHK, etc. (Also has worse input lag).

Hope this is a consideration in the future. Especially given all the interest in XLibre.

[JoshStrobl]

No, we are absolutely not going to reconsider not supporting XLibre. XLibre isn't going to be a successor to Wayland, the ecosystem has solidified around Wayland and standardizing protocols. The model of being able to implement compositors or support multiple compositors so long as they support similar or identical protocols is an objectively superior model to monolithic display servers (that end up doing far more than they should).

Budgie 10 will not support X11 (or any forks such as xlibre) in 10.10 and beyond. Budgie 11 and beyond never will either.

Wayland is not great for the user, especially people who have disabilities

If there are specific issues related to accessibility, this is something that the community will solve together by improving standardized protocols and improving accessibility tooling.

And wayland doesn't (And will probably never) cover all common use cases, especially for gaming like auto clickers, macro software like AHK, etc. (Also has worse input lag).

This isn't true at all. There are autoclickers that function under Wayland. They use either wlr virtual pointer protocol or libinput to accomplish it. For AHK, there's ydotool.