Official Wayland Support Postponed From GNOME 3.12 77
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."
Re: (Score:3)
Patches are welcome. =)
This is surprising (Score:3, Funny)
Re:This is surprising (Score:5, Funny)
At the risk of stating the obvious, prepare to have your hopes crushed.
Re: (Score:3)
I don't believe that by adding Wayland support they were going to - at least immediately - remove X support... But I was rather anxious to see Wayland support in it and test it in our distro.
On a different off-topic matter, it would be fun if they named it Wayland & Yutani, instead of Wayland & Weston.
Bad options for users (Score:5, Funny)
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: (Score:1)
I heard Gnome was going to remove the panel, wallpapers, and pretty much everything. They are going to have just one extra large button in the middle of the desktop with the label "NO" on it.. Some Gnome developers think that is going to be too confusing for the users so they want to get rid of the button, too.
No matter, GNOME, no thank you (Score:5, Insightful)
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 (Score:5, Interesting)
You should give cinnamon a try, it is quite good.
Re: (Score:2)
Re: (Score:2)
Well I did not notice any slowdowns on my core i5 laptop, but it does crash somewhat often (once a week, I just run the command to restart cinnamon and comes back to life with all my stuff still open, so no big deal). But someone else mentioned the battery life loss and while I haven't tested against other window managers I did notice my battery draining somewhat fast.
Re: (Score:3, Interesting)
I really don't get all this hate against Gnome 3. It's quite different, for sure and maybe it messes up someone's workflow, but at some point it will always be impossible to evolve without messing up at least some of the workflow and without making some people get used to different paradigms. I adapted quite well to Gnome 3 and am a happy Gnome 3 user. The new flow actually made me quite more productive.
Not trying to impose anything on anyone, but most of what I've seen so far borders an exagerated misguide
Re: (Score:2)
I like it a lot too. On both my netbook, notebook, and large double-monitor rig. The first thing I do after I install Ubuntu is install Gnome 3. Also when I do this for other people I turn on to Ubuntu for the first time, it has been a hit with everyone so far.
Your anecdote may vary from mine. But this is mine. I tried it compared to everything else and I like it.
Re: (Score:2)
but at some point it will always be impossible to evolve without messing up at least some of the workflow and without making some people get used to different paradigms
Why is "evolving" necessary? Some of us want tools, not eye sores^w candy.
There's no inherent advantage in having a desktop that looks like Windows, a Mac, or a cell phone.
Re: (Score:2)
Which I assume is why GNOME looks like none of those things.
Isn't a default GNOME screen completely blank? that's not really eye candy at all.
Note, I hate GNOME 3, and love a cluttered desktop, but a lot of people get annoyed by desktop clutter.
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
I really don't get all this hate against Gnome 3
They designed it to compete with the upcoming windows 8, they didnt want to get left behind (true story).
Re: (Score:2)
Not quite sure what you're on about. I was pretty careful not to put any hate whatsoever into the comment. I'm past anything like that, personally. I didn't (and don't) even recommend that no one else use it, or touch on any pros and cons. All I said is I am done with it. It is irrelevant to me.
Re: (Score:2)
Not accusing you of hating Gnome 3, your comment just reminded me of that.
Re: (Score:3)
I ditched GNOME for MATE about two weeks ago. A few bugs (e.g., screensaver timer is off), but also fixes things that have been broken in GNOME for years (single left-click on window list to pop something up, vs. right click and pick a menu option).
Restoring my customizations was surprisingly easy - easier than restoring them after the last few GNOME upgrades.
No regrets whatsoever.
Re: (Score:2)
Re: (Score:2)
Oh? I really want a patch to restore BBC, it gave really accurate weather for my area, and wetter.com not only was making up the weather prediction, it also gives multiple connection problems.
Can I have that patch to apply it locally, or is it still a WIP?
I love the weather app when it's not using wetter.com, it's been there in my system tray ever since it was possible to add it to the system tray. Can't wait to have it back with accurate predictions!
Re: (Score:2)
I think I can describe what was behind my rather rude description. The only reason I mentioned it is that there isn't that much to find fault with in KDE.
I compare the applet to the GNOME2 weather applet, which to me is perfect.
GNOME2: everything I care about is right there. Current temperature, wind speed and direction, dew point, whether it is fair or stormy. A nice succinct text forecast that includes expected snow accumulation if relevant. Weather radar. I think that's pretty much it; I haven't seen the
The real reason for the delay (Score:4, Funny)
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!
Better title (Score:1)
Wayland Waylaid by GNOME
Re: (Score:2, Insightful)
Change, because... change!
Re: (Score:2)
Oooh, Shiny(tm)!
Re:Could somebody explain wayland, please? (Score:4, Informative)
Re: (Score:2)
Re: (Score:2, Informative)
__WHY__
X is a farcical, bloated mess that sucks. A lot.
Some X developers (real, credible ones) saw what Apple has accomplished with their high quality compositors and correctly factored display stack and are trying to bring that to open source systems.
Re: (Score:3)
> Some X developers (real, credible ones) saw what Apple has accomplished with their high quality compositors and correctly factored display stack and are trying to bring that to open source systems.
Which is what exactly? I've owned Macs and I really don't see the appeal. If anything, Enlightenment blew the whole lot out of the water back in the 90s and made the whole idea of eye candy on the desktop a stale idea.
Copy Apple? Stop swimming in the Kool-aid.
Re: (Score:1)
Enlightenment was nice, but it wasn't perfectly smooth. Wayland, by having things render more directly, is supposed to fix this (like Windows Vista, and OS X have). There's a reason why Enlightenment is on the forefront of adopting Wayland.
Re: (Score:2)
I find the best approach in ANY OS is to avoid the obvious crap. Avoid the brand that performs the worst in the industry. Avoid the brand that has the worst drivers.
Good hardware and a well supported driver is 100x more effective than any attempt to pretend Apple is doing things the right way.
This Wayland nonsense is essentially trying to flush all that and set thing back to the 90s (in multiple ways).
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
Re: (Score:2)
What about tomorrow's desktops?
Re: (Score:2)
Re: (Score:1)
But they had the fathom to make a nice and extendable protocol. For example, when people figured out 10 years ago that the old rendering model is not the most approbriate, the Xrender extension was created. The Wayland FAQ acknowledges that you can do everything Wayland does by extending X (and it seems this is what the DRI3 extension is about). The only point of Wayland - and this is openlly admitted in their FAQ - is to get rid of old code by breaking compatibility in the long run. I do not agree with th
Re: (Score:2)
100% true. Because I spend most of my time on Linux playing high FPS games and doing other things in 3D. And X over network is simply an outdated concept noone needs.
Oh, wait...
Remote X is one of the things I find best in Linux. No cludges, no tricks - the UI is simply rendered remotely and one of the windows on my desktop is actually for an app running somewhere else. Nothing in the app to support this. No special tools in the system. Just basic X functionality. Cool! On the other hand 3D applications are
Re: (Score:2)
Remote X is one of the things I find best in Linux. No cludges, no tricks - the UI is simply rendered remotely and one of the windows on my desktop is actually for an app running somewhere else. Nothing in the app to support this. No special tools in the system. Just basic X functionality. Cool! On the other hand 3D applications are mostly eyecandy for this platform. Something to play with while something else is doing the stuff you need.
This is sad. I guess I should back to Windows then? What about us desktop users who don't want a gaming console + TV or whatever. Yes I want to play high fps FPS games and they have to work right, with non buggy drivers. I would even like being able to enable anti-aliasing but that's not a priority for people who develop open source drivers, hell there's not even a GUI.
On the other if I go back to Windows I'll still be able to run an X server and have a remote app show up, nothing special needed.
Re:Could somebody explain wayland, please? (Score:5, Insightful)
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.
Re: (Score:2)
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.
You're right! I don't actually need remote windowing, I'm glad that's cleared up.
Sarcasm aside, the Wayland folks have also had their own FUD and deceptiveness which means any hostility has been bolstered by a healthy dose of suspicion.
Re: (Score:3)
You're right! I don't actually need remote windowing, I'm glad that's cleared up.
And a perfect example of a peanut gallery comment right there. Somehow people think just because a remote window isn't defined in the underlying display protocol it won't work. That would be news to Microsoft, Citrix, VNC and pretty much everyone except for the "Coalition of Wayland Is Bad" who seem to believe that everything must be defined in the display protocol or else it won't exist.
Now the actual reality is that with Wayland the client now has the choice to implement VNC, RDP, whateverthefucktheywant,
Re: (Score:2)
> Nobody uses Weston so the fact it has RDP support is dick all use to anyone using GNOME or KDE.
Ding ding ding. This, here, is what I think is the main problem with the Wayland ecosystem as it currently exists.
As things currently stand, the Wayland protocol is designed to give compositors a lot of flexibility in what kind of buffers they support, with what capabilities.
The drawback is fragmentation.
So okay, the Unix world at large is not a newcomer to fragmentation issues. But it's still a problem that
Re: (Score:3)
And a perfect example of a peanut gallery comment right there. Somehow people think just because a remote window isn't defined in the underlying display protocol it won't work. That would be news to Microsoft, Citrix, VNC and pretty much everyone except for the "Coalition of Wayland Is Bad" who seem to believe that everything must be defined in the display protocol or else it won't exist.
Well, this is the stupid FUD of the wayland crew showing its ugly head again.
No one is stupid enought to claim remote win
Re: (Score:2)
> It will, however suck just as hard as all the other pixel-scrapers.
You are doing the same thing again.
You are asserting, without proof, that Wayland remoting will necessarily have to work as a pixel scrapper.
Wayland is designed to be extensible with regards to supported buffer types. For instance, YUV video buffers were merged into the reference compositor at some point in 2012.
And remoting specific buffer types can be done vastly more efficiently than with a generic pixel scrapper.
For instance, in cas
Re: (Score:2)
On that topic you have Wayland developers claiming stuff like X11 remote windowing is the "worst". This leads old X11 users to believe they are either liars or incompetent (and hence the lack of trust) because having experienced them all over many years, I know for a fact it is a long way from the worst.
I think you've touched on something there. "Old" that's a good term there. X *WAS* the fastest window manager of it's time over the network. For many years it had the best latency and speed, you know back in the old days when X considered of a client telling the display server to draw primitives, it was really fast and worked very well over the network. Unfortunately that system is not compatible with any modern usage of a GUI and that's not how it's done anymore. X11 now pixel scrapes, and sends the data o
Re: (Score:2)
Hi! I would have liked to thank you for taking the time to reply, but I find it difficult to do sincerely, because your comment adds nothing to the discussion, and even detracts from it.
You appear to be trying to imply, with some aggressiveness, that Wayland precludes remoting.
You could have expressed this concern as an interrogation, and I would gladly have tried to share what I understand about the topic.
Instead, no, a bold, unsubstantiated, sarcastic claim with no room for discussion. This is exactly wha
Re: (Score:2)
Instead, no, a bold, unsubstantiated, sarcastic claim with no room for discussion. This is exactly what I meant about the peanut gallery.
Apologies, now I have given a more detailed reply to someone else.
Basically, the best remoting by far is NX which has it at protocol level. Wayland is a pixel buffer level protocol. Basically that precludes anything better than VNC, which sucks.
Likewise, the fact you refer to the issues the Xorg developers themselves -- you are aware that they are who you refer to as 'the
Re: (Score:1)
I like the X protocol, one has to use XCB though, to see that it is really nice and well designed. What people call bloat is actually some code needed for backwards compatibility. There is really no bloat in terms of memory or cpu use. DRI3 will bring efficient buffer sharing for local clients similar to Wayland while still maintaining compatibility. Not that I care about these optimizations - I would prefer the Intel guys fix their drivers so that I don't have rendering bugs all the time on my notebook. (
Re: (Score:3)
Hi! Thank you for taking the time to reply.
I don't personally know the X protocol well enough to comment either way; I can only report on the opinion professed by the X developers themselves.
Here is what I understand are the answers to the points you raise. You'll probably want to check out the talks by Daniel Stone (core Xorg developer) that have been linked elsewhere in the thread, in case I missed something.
Essentially, their opinion is that the X protocol is unsuited to what computers do nowadays. From
Re: (Score:2)
Hi, I have to catch a flight. No time to discuss this now. But somehow you think the Wayland developers are "the X developers", who gave up on X. Some Wayland developers are also X developers would be more accurate. And there are other X developers who don't work on Wayland. And even the Wayland developers do not really claim that X is unsuitable for a modern desktops. Just check the Wayland FAQ: it spells out pretty explicitely that you could do everything Wayland does also within X. They just want to get
Re: (Score:3)
Hi,
Thank you for the additional details. You are right -- I meant to make it clear that the Wayland design was thought up by people with some serious experience of the internals and limitations of X, and not a competing team of newcomers, as appears to be assumed all too often. But yes, things aren't as simple as I made them look and there is only a partial overlap between the Wayland devs and the Xorgs devs. Thank you for the correction.
I also agree that Wayland is largely about canning the legacy in order
Re: (Score:1)
Then after Wayland developers produced their streamlined display server it turned out it didn't implement half the things real desktops need, causing the GNOME Wayland support to be delayed for another 6 months while the developers frantically try to reimplement 34 years of code.
Gnome 3.12 still supports Wayland (Score:2)
Gnome 3.12 still supports Wayland, for any distro that wants to ship it that way. It's just that Wayland is not the default for Gnome 3.12. This probably speaks more to the distros ability to have Wayland working smoothly than Gnome 3.12 using Wayland.
Missing feature like DND (Score:1)
Are you guys serious? Calling that a feature?
It's a sine qua non (wiki there to help you) you fraudulent wannabees!
In other words... (Score:5, Funny)
Wayland waylaid; now way late.
Give GNOME some credit and trust them (Score:1, Troll)
Re: (Score:1, Insightful)
Fuck that!
I was a GNOME user since before GTK+2 existed. I used GNOME2 for its entire life and it was exactly what I needed from a desktop environment.
Then the GNOME team got hijacked by a bunch of UI people obsessed with bringing the tablet braindamage to the desktop. Epic fail. Guess what, some of use use their computers to do REAL WORK.
I switched to a tiling window manager and haven't looked back. I suppose that I can thank the fecal encephalopathy of everyone on the GNOME3 team for helping me make t