Exactly, why make such a big issue out of this, when the target is so far away ?
Originally Posted by energyman
Originally Posted by China_Guy
hm, low performance and monthly driver rewrites (which fits nicely with intel's inability to provide good working windows drivers). No thank you.
Catalyst works fine. The open source drivers come along fine. Wayland is a Phoronix wet dream that might or might not become important in a very distant future.
A number of companies that write code and invest in it disagree.
Originally Posted by energyman
I was under the impression that the major players are adopting a mildly optimistic "wait-and-see" strategy, actually.
Originally Posted by 89c51
The number of people regularly contributing to Wayland is tiny. I don't mind the slow pace, if they are really going to completely re-arrange the way GUI works on Linux, I'd rather that they get it right than rush something half-baked. The major (promised) advantages of Wayland are primarily infrastructural -- cleaner code, less cruft, more direct interfaces, the actual benefits for the end-user will not be huge performance improvements (all relevant stuff like 3d and GUI toolkits can bypass X almost completely already), but hopefully more stability and reliability. And this takes TIME.
I don't know, it seems reasonable.
Simpler code is easier to maintain, and all the important stuff has been moving out of X for decades: GUI, 3D, modesetting, font management... Lots of stuff in X is very rarely used and it would make sense to move it into an optional (but still available!!!!) codepath, in order to keep the daily bread and butter simple and maintainable.
The fact that Michael tries to sell every indentation change as the second coming of Jesus, while shitting on much more excising progress in the kernel and Mesa, that's a different problem. I think that if you look outside of phoronix and check the opinions of kernel, Mesa and X developers, you'll find the ideas behind Wayland much more palatable. Of course, it will take time, and it's still undecided whether it will be a real benefit when it finally arrives (and compared to the improvements that X will undergo in the meantime). But when that happens, distros will have a look and decide for themselves.
Just ignore the Wine kiddies who think this will magically improve their gamez and wait and see, that seems to me the best approach.
wayland is not a wet dream or useless, wayland is the future and many parties are extremely interested in get it done and when done will improve our graphic stack awesomely but this doesn't mean we hate X11 or anything like that but the problem is that X11 was not designed for this age sure has been a long and funny trip and we all should feel nothing but respect for the old dependable X11 but sadly X11 reached an age where it can no longer speak efficiently to modern GPUs and slowly but surely is becoming a white mammut.
Originally Posted by energyman
wayland on the other hand is designed to be as minimalistic and unintrusive as posible while let you exploit the modern GPU capabilities, sure it miss some thing like network rendering but if you think hard about it this should be done at toolkit level and using third parties security measure like kerberos and tls/ssl [i admit X11 net rendering is cool but security isn't exactly its forte] because logically QT/Gtk/e17/etc crowd know better how to efficiently send the data for a remote server to render[remember wayland don't have a rendering API per se] than wayland because wayland is just a protocol and don't know what are you doing with your drawing API[egl,opengl es, opengl, openvg ,etc] beyond provide framebuffer control.
wayland rise does not mean X11 fall cuz X11 is needed by many commercial apps today[and i bet redhat won't migrate anytime soon due to their LTS system], it just means a new more effcient tecnology will enter in testing phase alongside with X11 until is able to replace it[well if you dont depend on X11 you can switch faster if not you have Xwayland or just stay with X11 as long as you like no one is forcing you to migrate and distros will provide both for quite some time so no biggie]
have you read the wayland protocol??
Originally Posted by BO$$
you have any sort of idea of the difference between wayland and X11??
you understand why wayland propose such a radical change of POV compared to the X11 paradigm[well OS X did something similar]?
"It's just so programmers feel good reinventing the wheel of course using the "this time we will design it better" mantra, where design is something they don't really bother to define so that it means whatever they want it to mean" <---WTF?? http://wayland.freedesktop.org/architecture.html [you google kung-fu is weak]and in http://wayland.freedesktop.org you can find FAQs, mailing list and the actual source code amazing right?
i guess you are another less bash about something you don't understand just for the sake of posting?
ofc when wayland reaches 1.0 release it won't save kittens from trees and cure the cancer or help in the discover of cold fussion cuz as any software developers need time to adapt to the new way.
about games wayland is not a game engine nor is opengl implementation because that is mesa/libgl work not wayland or X11[dunno how somebody related this 2 things togheter but well] about wine is another story but in the 2d section[wine or not 3d is handled by mesa/libgl] cuz a smart implementation could help a lot the performance rendering of wine[Qt/GTK/e17/etc too] due to wayland flexibility and modern GPU capabilities, read wayland site and try to figure out why!!
At the same time, there's a community around X vs a few developers around Wayland. A cleaner code base is definitely desirable, but it doesn't come for free, unfortunately. It's only going to be a bumpy road in the beginning though, new contributors will more likely choose the project with a lower entry barrier.
Originally Posted by pingufunkybeat
08-22-2012, 12:37 PM
Since we all know what Wayland is and does, one of the stock questions I set out to answer was "What problems does Wayland intend solve for users and developers"?
I'll post when I find an answer. Meanwhile, the LWN articles are fairly interesting.