Can't wait to see how little the performance boost is over X so we can finally conclude Wayland is dead on arrival after all those years of shilling.

>>51930675
plasma blows kde4 is a lot better

>KEKDE

It will be interesting to see Fedora 24, when Wayland becomes default

>still unusable trash that eats up memory

wew lad

But what is wrong with Xorg?

>>51930760
With driver support going through the plughole? Proprietary drivers don't support Wayland natively so you're stuck with hacked-together solutions or the poor nouveau drivers when on nvidya with its "fuck open-source" mentality. Good lord.

>>51930781
input and rendering lag. Window tearing. Incredibly bloating and overly complicated. Apparently only 3 people understand why everything is written the way it is from top to bottom. It's not sustainable going forward.

>>51930691
Are you retarded? Wayland was not made to outperform Xorg like that.

>>51930796
Can wayland not switch to software compositing when needed?

>>51930841
Then what's the point for the end-user? I mean, there has to be a point for the average Linux user, right? Other than complicating things even more with yet another part that makes up the GNU/Linux ecosystem.

>>51930796
At least Nvidia have been working on non-free Wayland drivers for awhile.

How long until Ubuntu abandons Mir as a huge mistake?

>>51930913
Never, phone is more important than Desktop according to Canonical.

>>51930913
It already did?
ubuntu 15 uses wayland?

>>51930940
They're dead on arrival on phones. Literally 0% chance of making an meaningful progress there. Who would want that?

>>51930949
Interesting. Not really sure what they did though. They just added the wayland packages in the distro? Unity is not supporting Wayland any time soon from what I can see.

>>51930865
The point is having desktop environments and window managers that actually control the desktop and its windows. With X being what it is, even "simple" things like lock screens, fullscreen modes and vsync are full of weird glitchy corner cases because window events and rendering have to jump through too many hoops that were never meant to handle that shit in the first place.

For example, if you have an application running in fullscreen mode and the lock screen is activated, in current X-based desktops there's no telling if the lock screen is going to work properly or not; from X's point of view it's just another window, no matter how hard the DE tries to make it dominant. Depending on how the fullscreen application did its X fullscreen window magic, the lock screen's X incantations may prove ineffective and some input may fall through the lock screen (this may depend on the type of input device since they're handled by different code). It's kind of like old Unity games poking their shitty GUI library in weird ways hoping it'll cooperate.

Then there's the obvious security implications: Anything with X access can't be sandboxed because it can mess with the event handling as it pleases.

>>51930949
16.4 is on mir

Can wayland play anime?

>>51931024
>Unity is not supporting Wayland any time soon from what I can see.
There are other options than Unity, son.

>>51931076
Is wayland one of them?

>>51931062
Can you play dead?

Proprietary nvidia wayland drivers when?