AMD Catalyst Will Not Support Wayland Anytime Soon

[LinuxID10T]

MSAA offers better image quality at a higher performance cost and is still the defacto AA stadard. The newer AAs are almost all based around doing a quick messy job and the choice is yours where you draw the performance / image quality line. It has nothing to do with MSAA being primitive.

Course, neither really compares to a higher res screen. The death of AA can't come soon enough, in my opinion.

I really wouldn't mind some SSAA and I know they are working on MLAA but MLAA has some problems. Even on a high res screen though, you will still want AA. Even on 300+ DPI screens, AA is noticeable.

[russofris]

Course, neither really compares to a higher res screen. The death of AA can't come soon enough, in my opinion.

The end of AA will be the beginning of scaling/filtering/postprocessing. We'll see an brief technology arms race as GPU designers do their best to make old assets look good on new hi-ppi displays (like the fake 2.5D on 3D television tech race). It might be a fun time, it might be a horrible time.

We'll likely see resolutions stabilize at 2k and 4k, followed by exponential increases in scene complexity as outward scaling GPUs and CPUs begin to share memory.

After that, it's probably going to paradigm shift towards LF rendering, or voxels/rays, or some other emergent fringe tech. I've seen a number of compelling LF expositions out of Stanford and MIT in the past few years. Neat stuff.

[russofris]

Even on 300+ DPI screens, AA is noticeable.

I would appreciate it if you could convince me, as it is the opposite of the conclusion that I reached when evaluating retina.

If I cannot perceive the pixels, there's no "aliasing" to begin with when rendering at the screen's native resolution. Perhaps "when rendering at the screens native resolution" is the cause of our opposing perceptions. I would concede that your statement holds true when rendering below the native resolution, as we can demonstrate its benefits without high-ppi displays.

F

[vortex]

who the fuck cares? really? It will take years until wayland is ready for the masses - and I still don't understand what is so great about it.

So if it is years away and doesn't even have an api yet, why should nvidia or amd waste precious (and expensive) ressources on it, as long as their is X11 stuff to be done?

Exactly, why make such a big issue out of this, when the target is so far away ?

[energyman]

fortunately, I ONLY use PC of "Intel inside" exclusively,I own a Intel ivb now without any discrete GPU! I'm very satisfied!I'm looking for default Intel driver for Wayland!!!

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.

[89c51]

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.

[pingufunkybeat]

A number of companies that write code and invest in it disagree.

I was under the impression that the major players are adopting a mildly optimistic "wait-and-see" strategy, actually.

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.

[BO$$]

I'll say it again: Wayland does not feature serious improvements for the end user. It's just for the code monkeys to have something to masturbate over. 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.

[pingufunkybeat]

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.

[jrch2k8]

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.

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.

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]