Slashdot Mirror
GNOME Aiming For Full Wayland Support by Spring 2014
An anonymous reader writes "Canonical's plan to develop the Mir Display Server for Ubuntu rather than going with their original plans to adopt Wayland has been met with criticism from KDE (and other) developers... The GNOME response to Ubuntu's Mir is that they will now be rushing support for the GNOME desktop on Wayland. Over the next two release cycles they plan to iron out the Wayland support for the GNOME Shell, the GTK+ toolkit, and all GNOME packages so that by this time next year you can be running GNOME entirely on Wayland while still having X11 fall-back support."
For the record, as long as whatever display system we settle on provides network transparency for all applications, I don't care what's behind the hood.
Give me Classic Slashdot or give me death!
Can't speak for the GP, but in my case, yes.
Yes, by all means spam me now with all the arguments that claim that X11 is terrible because it's imperfect. I'm well aware it's imperfect.
But the fact is it's not imperfect enough to warrant throwing it out and replacing it with something that lacks the more awesome things X11 does. Yes, I know the counter argument here too: "Nobody uses/needs/wants the awesome things!" says Baby Bathwater. But look at what you're proposing: a tiny, inconsequential, performance improvement and possibly cleaner API, in exchange for guaranteed incompatabilities and the removal of functionality.
So, pretty please, knock it off with the Wayland/Mir shit, at least until you achieve feature parity.
You are not alone. This is not normal. None of this is normal.
Because if you have network transparency in the display system then all your applications get network transparency for free. They just talk to the display system like they always do and the display system throws them up anywhere you're connected to, as you like.
Except if you have very little bandwidth it is absolutely horrible and you'd do far better with a web interface and if you have lots of bandwidth you can use VNC. The pipe between your CPU/RAM and GPU is one of the fattest pipes in a computer able to push many GB/s and when you replace that with tin cans and a string you need to do something, it's like arguing that if I replace your graphics card so the game renders at 1 FPS that it's now supported for free. I'd never, ever design a system that'd depend on X11 for remote access, would you?
Live today, because you never know what tomorrow brings
And relying on a bloated 3d stack just to draw a damn window isn't a bottleneck?
Face it, the only people that want to replace X which works JUST FINE are people who want to play with their goddamn wobbly windows. We get enough of that garbage with compositing, thanks.
This is what I hear when I listen to X11 zealots:
I DEMAND THE RIGHT TO USE MY 1988 MOTIF APPLICATION OVER A 28K modem connection AND FUCK ALL OF YOU WHO WANT A MODERN DESKTOP WITH A CODE BASE THAT CAN BE MAINTAINED AND IMPROVED.
It looks to me that Wayland developers only have one desktop at home and were Windows users that want gaming on their linux box.
- What about asynchronous rendering? fast text scrolling in a windows like "find /" or "make -j32" thru a modem connection works in X11, I'd be surprised to see the same on Wayland.
- What about single GUI App running remotely: ssh to a cluster with no network card and need to start paraview or gnuplot? Should I run a full desktop with useless fancy gadgets just to see a gnuplot window?
- What about client application that freeze: Can't move the window because the decoration is done by the client?
- Wy can't I move parent windows when a modal window is open like a file selection dialog box. How do I move the parent app to see my shell window behind. Should I do the same as in windows: close the file selection dialog box move the windows and reopen the file selection dialog box?
- What about lost event because the client is buzy? I click on the button, but the event is lost because the client is buzy.....
Wayland is just a LOL in professional environment.
Thanksfully, I'm running KDE...The original desktop that Gnome tries to imitate since it's creation...I'm curious how it's manage the Wayland migration....