GNOME X.Org vs. Wayland Performance + Power Usage On Fedora 32 With AMD Renoir Laptop

[jrch2k8]

Well. This thread has become litigation grade proof that most people posting here don't have even slightest idea of what is X11 or wayland are and/or why you are comparing Gnome Vs Gnome and Firefox Vs Firefox and/or whereas the protocol backend uses Wayland or Arcan or X11 the actual performance/RAM/etc. won't vary much if at all.

[andyprough]

There's nothing to configure moron. It plays nicely under Wayland.

I'm the moron? Who's the one who can't figure out how to play Quake correctly after 30 years of trying?

[duby229]

While technically wayland might be 12 years old, the accompanying compositors are far from that. And that is what matters. Look, wayland has the broad support from the industry. It's used in car infotainment systems, it's used in phones and now it's starting to be used on the Linux desktop. It will even be used on Windows through the means of WSL2 in order to support graphical applications. All of you that state that "wayland is already 12 years old and nowhere to be seen" have the wrong perspective. Replacing something so fundamentally as the display system in an operating system is a gargantuan task that takes a long time. And that time is far from being 12 years yet. More honest would be to start counting from the first release of Gnome that supported wayland.

Yeah and it was -designed- for extremely simple use cases like car interfaces or kiosks. It just doesn't have to design scope to fulfill the needs of a desktop operating system.

[duby229]

That is the right attitude.



As I said. I think it's dishonest to claim that it has been 12 years. Or even 10. A specification of a protocol being 12 years old has nothing to do with the state of the compositors implementing that specification. The first gnome release with support for wayland was 4 years ago. Also, I realize that replacing something as fundamental as the display system is not going to be done just like that. Perhaps it's because I have programming as a profession myself, but I'm not that surprised that wayland is taking this long time to gradually replace a beast like X11, and also that it's not there yet for all (relevant) use cases. It will be, however. Eventually.

Saying that it will get there "eventually" is dishonest at best. It simply doesn't have the design scope to be capable of getting there. It wasn't made to be able to get there.

[Guest]

There's nothing to configure moron. It plays nicely under Wayland.

Well, this ALT+Tab issue, for certain apps-only, you're pointing out, isn't that much of UX drawback,... However, I had to switch from Wayland back to X11, because it didn't support screensharing, which I occasionally very much need for remote work. So, unless screensharing works flawlessly in Wayland, I'm staying with X11.

[Grim85]

Wayland has 0 good implementations and by design can never have a good implementation

X11 has 0 good implementations and by design can never had a good implementation.

Wayland doesn't work today, X11 does. Both are crap but one works now. Hopefully Arcan can fix this mess since Mir is dead.

No one is stopping your from contributing fixes to relevant git trees

[tomas]

Yeah and it was -designed- for extremely simple use cases like car interfaces or kiosks. It just doesn't have to design scope to fulfill the needs of a desktop operating system.

And what is it that you believe is missing? And please don't say "network transparency"?
Someone mentioned "color management" earlier. That is currently proposed as a protocol extension:

https://www.phoronix.com/scan.php?page=news_item&px=Wayland-Color-Manager-Calibrate

https://lists.freedesktop.org/archives/wayland-devel/2019-April/040431.html

So that is at least one thing that is currently missing. Anything else?

[Volta]

I'm the moron? Who's the one who can't figure out how to play Quake correctly after 30 years of trying?

You're the one who didn't figure out how to use Wayland after 12 years of trying. This is the essence of your logic. What recommendation could you give me? Change number of bots, their level, game mode, perhaps? Will this fix broken X that captures mouse for no reason?

[Volta]

Well, this ALT+Tab issue, for certain apps-only, you're pointing out, isn't that much of UX drawback,... However, I had to switch from Wayland back to X11, because it didn't support screensharing, which I occasionally very much need for remote work. So, unless screensharing works flawlessly in Wayland, I'm staying with X11.

The lack of screen sharing is a fact. However, in the same DE under Wayland I can use Alt+Tab without issues. The same people blaming Wayland ignore the fact the problem may lie in Firefox, Mutter etc. This analogy gives them a correct label. They're blaming Wayland for not being drop in replacement. It puts more work on others, so if they are Firefox, Gnome, KDE developers I understand their whining. However, it seems they're not and real KDE, Gnome, Firefox developers are fine with Wayland and they decided to port their projects, so WTF those looser are whining about? The only answer that comes to mind is: Gnome, KDE, Firefox devs. You're too slow and you suck! This is the real message of Vistaus , andyprough , Guest etc.

[tildearrow]

DanL Read the source It’s mostly about Xwayland and cutting support

You think that makes me happy? (to lose support for X11 apps that still have not been ported to Wayland)

It doesn't. :l