Advantages of Wayland over X11
- Thread starter dos2unix
- Start date
I've been daily driving Wayland since I bought my new system, which is 5 months ago and I've never had had to switch to X11/Xorg since.
@f33dm3bits,
now its time to list your complete HW in detail.
now its time to list your complete HW in detail.
AMD Ryzen 9 7900X
ASUS ROG Strix B650E-F GAMING WIFI
Sapphire Nitro+ AMD Radeon RX 7900 XTX Vapor-X 24GB
Corsair 4000D Airflow Tempered Glass
Arctic Liquid Freezer III 280
Corsair Vengeance CMK32G
ASUS ROG Strix 1000W Gold Aura Edition
Samsung 980 Pro 2TB
I've used both Fedora Silverblue(Gnome) and Arch Linux(Gnome) with it just normal install nothing special or customized.
Last edited:
CaffeineAddict
Well-Known Member
Probably because of AMD GPU, you were using Nvidia before right? and then Wayland didn't work?
I had an Nvidia GPU before, was using Wayland then as well but only thing that had a problem was that Steam glitch with Wayland so technically have probably been using Wayland for a bit longer. I've heard the recent 555 driver updates with new gpu's have give most people a lot better Wayland experience. My Nvidia RTX 3090 is eating dust lol.
Last edited:
CaffeineAddict
Well-Known Member
Strange because I'm also on Debian 12 with KDE but I had problems.
Drag & Drop bookmarks in Firefox does not work for instance.
Yes Shift + Del is a shortcut to permanently delete a file (without moving to trash)
You should state your GPU, Desktop and GPU driver at least.
Well can't speak to that don't use FF much these days as I prefer Vivaldi. So haven't tried what your having problems with.
Last edited:
wow, seriously? I am not sure but I think I am offended by that comment.
Same here, I think this is one of those times when what distro you run makes a difference, also likely which desktop you run.
A possibility. I also am running Radeons these days. My Geforce bit the dust a while back.
For the same price point, the Radeons were outperforming the GeForces, but that's not true if you
move up into the higher price points ( GeForce 4080 and 4090 )
what is your problem? this is supposed to be friendly here and you clearly are not. Why the hostility?
I am sorry, I did only reflect this reply by ATPI :
"somehow I do not think wayland will ever meet your rigid requirements. complete and stable? you sure are holding them to one amazingly high standard there aren't you."
It compares SW-Developement against a person, and it is not sarcasm.
Last edited:
that sounds very appealing, but why is X11 still the dominant windowing server even though it's decades old?
"Well, in situation a, X11 is better, but in situation b, wayland is better"
to me, it's structurally the same as the anti-systemd argument: yeah, it's an issue in the sense that it attaches itself to every process at startup, but where's the real problem? Every linux issue i have had had NOTHING to do with systemd.
also, and these are programming language debacles, but they appear to be just as strange: i read somewhere that goto labels in C are bad...for those of you who don't understand, this is how they work:
so, all programming languages are linear: the computer just reads the code from start to finish, BUT goto labels give you a way to go back to something or go towards something based on whatever happens. And the reasoning that "they are bad" is that they are inherently confusing and disrupt the linear flow of the program. However, I recently realized that in some situations they can actually reduce the amount of code in general, which for programmers, makes it less confusing...it 's not like "goto" is cryptic at all, or at least any more so than "if", "for", "while",....if you need further validation, here's an entire page worth of arguments as to why goto is not evil:
https://stackoverflow.com/questions...es-for-goto-in-a-language-that-supports-loops
and also, there's been this debate about whether Rust is superior to C because of "memory safety" because the white house said C is bad and programmers should change things over to Rust. However, C programming has been around since 1967, and it is still widely used in all sorts of applications: for example, the linux kernel developers found that Rust is better than C in certain situations, but the amount of C code they replaced in the process was laughably small. So, as a novice who knows that C memory allocation is a pain in butt and has no Rust experience, has led me to conclude that maybe...
the liberal use of memory management is also a disadvantage...but currently, you just can't do the same stuff with Rust, and Rust also has it's own security issues...
i mean, i really don't know the total depths of these things, but this is what i have gleaned: which is better just depends circumstance and preference. I'm not even going to go into the emacs vs. vim debate, the arguments probably are even more silly even though my preference is obvious (and yes i have messed around with emacs some and seems weird).
i generally find software debates in general, in the linux community, to be based on false dichotomies that don't serve a practical purpose. The best answer would most likely be something like:
"Well, in situation a, X11 is better, but in situation b, wayland is better"
to me, it's structurally the same as the anti-systemd argument: yeah, it's an issue in the sense that it attaches itself to every process at startup, but where's the real problem? Every linux issue i have had had NOTHING to do with systemd.
also, and these are programming language debacles, but they appear to be just as strange: i read somewhere that goto labels in C are bad...for those of you who don't understand, this is how they work:
Code:
paradise_island:
int come_to_paradise_island;
...
if(something is true or false)
goto paradise_island;so, all programming languages are linear: the computer just reads the code from start to finish, BUT goto labels give you a way to go back to something or go towards something based on whatever happens. And the reasoning that "they are bad" is that they are inherently confusing and disrupt the linear flow of the program. However, I recently realized that in some situations they can actually reduce the amount of code in general, which for programmers, makes it less confusing...it 's not like "goto" is cryptic at all, or at least any more so than "if", "for", "while",....if you need further validation, here's an entire page worth of arguments as to why goto is not evil:
https://stackoverflow.com/questions...es-for-goto-in-a-language-that-supports-loops
and also, there's been this debate about whether Rust is superior to C because of "memory safety" because the white house said C is bad and programmers should change things over to Rust. However, C programming has been around since 1967, and it is still widely used in all sorts of applications: for example, the linux kernel developers found that Rust is better than C in certain situations, but the amount of C code they replaced in the process was laughably small. So, as a novice who knows that C memory allocation is a pain in butt and has no Rust experience, has led me to conclude that maybe...
the liberal use of memory management is also a disadvantage...but currently, you just can't do the same stuff with Rust, and Rust also has it's own security issues...
i mean, i really don't know the total depths of these things, but this is what i have gleaned: which is better just depends circumstance and preference. I'm not even going to go into the emacs vs. vim debate, the arguments probably are even more silly even though my preference is obvious (and yes i have messed around with emacs some and seems weird).
