Yes he does. The mini timeline is in the main application bar
I didn’t read the entirety of the last report you mentioned ( experimental: Add xx-zones protocol for area-limited window positioning) nor do I completely understand the finer details of it since I’m not a GUI programmer, but it appears to have been merged in the “experimental” branch 3 days ago.
So if that has been a blocker when it comes to “I’d like to put this other window inside my main app window” then maybe this particular thing will be a non-issue in the future.
The guy who started Wayland, Kristian Høgsberg, was an prominent Xorg developer and concluded that it kinda was.
Or maybe not entirely broken and bloated but at least having band-aids upon other band-aids and lots of inherent security issues.
X11 has been around for 40 years so if no one has attended to any neglected areas already I don’t think anyone would be able to rally up a concerted effort to improve them.
XLibre could potentially be such an effort but if sMueggli’s analysis of Mr. Weigelt’s coding efforts is correct ( Gentoo Forums :: View topic - [split] On the future of X ) then it’s doubtful.
To quote from that post :
"Enrico Weigelt does not seem to test his own code and changes
He produces a lot of merge requests
A lot of ABI breaking changes without any benefit (for end users)
A lot of work for reviewers and in case of bug to write bug reports and bisecting
A lot of code is moved around, which does not solve a problem or bug, but only the position of the problem or bug in the code "
I would think that the chief Muckety Muks in the various major distros have noted that the last Xorg release was in 2012 and have decided that it’s not something their distro should rely upon going forward, in the same way very few distros nowadays use artsd as their sound server ![]()
EDIT: Maybe someone ( @seablade ?) could move the “X vs Wayland” posts here into a separate topic?
I really hope so, and I hope that applications like Kicad and Ardour, and the Valve initiative, raising some visibility of the situation will help nudge them in the right direction.
Yes. I didn’t mean that it had broken functionality, which is really what end-users, distro maintainers, and app developers see mostly, and care mostly about. I mean that it had major architecture, security, and code maintainability problems that were not going to go away, in some cases, even if there was a ground-up rewrite of the whole stack.
XOrg and it’s predecessors are amazing suites of software and related specifications. I remember astounding everyone in a NOC back in the mid-1990s when I demonstrated it was possible to launch almost any GUI onto any of the 20-odd screens in the NOC console (in the days when almost all the monitoring applications ran on Unix systems).
But life has moved on and, 30 years on from that, the X11 server architecture and all of its complexity and, frankly, hacks (Xv, Xinerama, XComposite, GLX, DRI3, XInput2, and VNC hacks, for example) really isn’t what’s needed on modern desktop environments, especially in this world where network and local security are increasingly important.
And the argument is that the distros and DEs want to start implementing new stuff that wasn’t possible or, at least, very difficult, lacking in performance, or requiring ugly hacks under X11 (such as efficient video encoding, remote desktops, low-latency gaming, proper HDR and colour management, fractional scaling, mixed and variable refresh rates, touchscreen gesture/kinetic scrolling support, etc.)
But, on the other hand, the replacement has to be fit-for-purpose and Wayland really doesn’t seem to be at this point. In the respect of functionality to support applications properly, Wayland does seem to be fundamentally “broken” at present.
I do wonder if the distros and DEs pushing for this to be the default is, in part, to surface some of these issues and/or to put pressure on the Wayland project to address and fix them.
+1
Cheers,
Keith
I’ll get off the merry go round now. Happy to acknowledge out of my depth with the technical details. I can only say in 20 years of using Linux and almost that many of preparing it for others to use Xorg has not been a significant problem (there have been plenty of others) and I’ve personally had several multi-head setups of my own with well-chosen and known-supported Video cards that in almost all cases didn’t even need the resolution set; turn on and go. Wayland today would break my system even though my DE has initial support for it, most Linux programs rely on X11 or XWayland and many Desktop Environments and Window managers still do and lack developer power to completely rebase. As a User I will say on a platform that blows it’s horn so loudly about freedom from proprietary overlords this top-down ‘assimilate or die’ vibe is very disconcerting. Although I’ve never been a Windows hater and still use it often I don’t really see that corporate Linux can really be throwing stones from their glass houses any more about Vendor lock-in. If X11 does indeed fully get replaced you’ll be forced to pick from a small pool of Desktop Environments, sure not as bad as being locked into one thing but it still feels very anathematic to what drew a lot of people (including myself) to Linux in the first place. Anyway, on to waiting for the Ardour 9 hotfix…
Given enough duct tape and crew men Titanic hitting the iceberg wouldn’t have been a problem for the passengers either ![]()
If the Xorg developers themselves think that X11 needs a replacement I think I would agree, even though I run X11 exclusively, with Compiz providing wobbly windows for my XFCE session, and I haven’t really tried Wayland since I made a script to download and compile its components back in 2013.
But one day I suppose I’ll have to make the switch. Presumably when XCFE has proper Wayland functionality and I’ve figured out if I can live without wobbly windows or not.
No one is preventing you from running X11 in the future; neither Red Hat, Canonical nor anyone else can stop you from doing that, since anyone can fork the Xorg code and continue to develop it.
But “freedom from proprietary overlords” has never been “all distros have to package the things I want”; they can of course decide which graphic system they want to support, so you may have to resort to a theoretical “DevuanX” or something if you really don’t want to touch anything Wayland.
When XFCE gets proper Wayland support I would think that the DEs a majority of the users are running will be covered.
Though several fvwm95 and WindowMaker users will probably be a bit upset when their favorite distro drops X11 (well, maybe they work just fine in XWayland, who knows) ![]()