Official Wayland Support Postponed From GNOME 3.12

An anonymous reader writes "GNOME 3.12 was going to have official Wayland support as one of its main features for the upcoming desktop release. The developers have now decided to delay the official Wayland support until at least GNOME 3.14 while the support found there will be shipped as a preview. Missing features like drag 'n' drop and clipboard support are still missing from GNOME's Wayland code, which made them decide another six months of development work is needed. Other GNOME 3.12 features are mentioned on the GNOME Wiki."

Comments

Bad options for users

[Anonymous Coward]

I thought Gnome was going to remove support for drag-n-drop and clipboard anyway. Those things are options in all other OSes, right? And they are too complicated and nobody uses them, right?

Re:This is surprising

[MrEricSir]

I hope this isn't because Wayland is that bad, but rather because the Gnome team has learned some lessons about removing the stuff that works and putting in stuff that is not ready for prime time yet.

At the risk of stating the obvious, prepare to have your hopes crushed.

No matter, GNOME, no thank you

[fnj]

I don't care what happens with GNOME at this point. I will be using either KDE or Xfce. I have been GNOME free for long enough to know that I am not going back. I evaluated Xfce long enough to know that it is quite satisfactory, if not as perfect as GNOME2 was. Now I have been on KDE for five weeks. I have issues with the control over icon placement on desktop and taskbar, and the putrid weather applet - otherwise, absolutely no issues whatever.

I'm afraid the MATE DE is not yet good enough to live with. I evaluated it; it is very promising; I support the effort, but it's no replacement for GNOME2 yet. I'm not sure anything will ever be, but that's life. No car is anywhere near as perfect as the glorious 1978-1982 Audi 5000 either, and nothing has come along to equal the late Icom IC-R75.

Re:No matter, GNOME, no thank you

[Daniel Hoffmann]

You should give cinnamon a try, it is quite good.

The real reason for the delay

[Anonymous Coward]

for i in /usr/bin /usr/sbin ; do
"${i}" --version
done

systemd 208
+PAM +LIBWRAP +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ ... ...

and once it reaches wayland the output says

wayland 1.10
not yet depending on systemd

The real reason!

Re:Could somebody explain wayland, please?

[JVolkman]

This video (from 2013) provides good information about the push towards Wayland: http://www.youtube.com/watch?v...

Re:Could somebody explain wayland, please?

[Balinares]

The story so far in a nutshell:

The Xorg developers got tired of spending their time working around the way X was designed in 1980 (which made sense at the time) to try and make it fit 2010 workloads and hardware.

They started to think about how to do the stuff that actually needs doing in an efficient manner, while removing the roadblocks they currently have to contend with.

Turns out that when you take what Xorg actually does nowadays, streamline the fuck out of it, and take away all the needless obstacles, you end up with a pretty straightforward buffer sharing protocol. They called it Wayland and started to work on an implementation.

And then the countless people in the peanut gallery who obviously know X much better than the X developers beheld the notion and started giving... loud feedback, shall we say. Without ever stepping forward to take over the maintenance of Xorg, mind you.

TL;DR: Xorg developers make what they concluded is the soundest technical choice. People on the Internet lose their shit. Business as usual.

In other words...

[fahrbot-bot]

Wayland waylaid; now way late.