You made a claim that Wayland is buggy when streaming and gaming. I told you I do both of these daily with Wayland.
What an intelligent person would do is recognize that they misunderstood the problem and that it was their particular setup, skills, or ability that caused the issues, not Wayland itself.
Expectedly, you realized it was a “you” issue enough to get mad, but not hold yourself accountable and admit Wayland was a red herring. Par for course based on the original claim.
What kind of “skill” or “me” issue is there with bugs? I make the windows flicker by sheer lack of skill? The Steam or Firefox windows stop updating because I have a “particular setup”? Those are bugs. I did not have these issues on Gnome X11.
Just stop and think a little.
edit: here is another anecdote from today. My son has different hardware than me, but also runs Gnome Wayland. He had an issue with his microphone in a game, it kept feeding into itself. So I alt-tabbed to check if the source that was active was the monitor of the microphone, since we were messing with easy effects earlier, and it was indeed still on monitor. I turned the monitor setting off and went back into the game. Now we had no mic input. No problem, let’s check again, we probably forgot to change the source from the monitor to the actual microphone. Alt-tab did nothing, Windows/Super key did nothing. He didn’t want to quit the game, so he continued as it was. Must be another skill issue, not being able to alt-tab or bring up the overview with the super key after doing it once. I still am going to pin this on “gaming using Gnome Wayland is buggy”.
Edit2: waaaiit, it just clicked. You’re one of those pedantic people. It’s not a “Wayland, the protocol”, issue, it’s a “Wayland implementation in gnome in combination with my hardware and selection of games and streaming software issue”! I hope that makes more sense. Sorry, I thought I could simplify it by the way I may have said it, I’m sure everyone else understood what I meant.
Based on what you’re saying, I don’t feel like you know enough about the subject matter to be forming such strong opinions.
You have no idea what went wrong yet seem confident what made things break. You are, simply put, hopelessly clueless, as evidenced by how you arbitrarily combine distros, desktops, and window managers when describing your issues. A more astute user would account for such obvious variables before jumping to conclusions.
Wayland is not responsible for the issues you’re describing. You’re just woefully stubborn and unwilling to be wrong. It’s fucking embarrassing and if you weren’t completely mentally spent, you would feel shame.
You made a claim that Wayland is buggy when streaming and gaming. I told you I do both of these daily with Wayland.
What an intelligent person would do is recognize that they misunderstood the problem and that it was their particular setup, skills, or ability that caused the issues, not Wayland itself.
Expectedly, you realized it was a “you” issue enough to get mad, but not hold yourself accountable and admit Wayland was a red herring. Par for course based on the original claim.
What kind of “skill” or “me” issue is there with bugs? I make the windows flicker by sheer lack of skill? The Steam or Firefox windows stop updating because I have a “particular setup”? Those are bugs. I did not have these issues on Gnome X11.
Just stop and think a little.
edit: here is another anecdote from today. My son has different hardware than me, but also runs Gnome Wayland. He had an issue with his microphone in a game, it kept feeding into itself. So I alt-tabbed to check if the source that was active was the monitor of the microphone, since we were messing with easy effects earlier, and it was indeed still on monitor. I turned the monitor setting off and went back into the game. Now we had no mic input. No problem, let’s check again, we probably forgot to change the source from the monitor to the actual microphone. Alt-tab did nothing, Windows/Super key did nothing. He didn’t want to quit the game, so he continued as it was. Must be another skill issue, not being able to alt-tab or bring up the overview with the super key after doing it once. I still am going to pin this on “gaming using Gnome Wayland is buggy”.
Edit2: waaaiit, it just clicked. You’re one of those pedantic people. It’s not a “Wayland, the protocol”, issue, it’s a “Wayland implementation in gnome in combination with my hardware and selection of games and streaming software issue”! I hope that makes more sense. Sorry, I thought I could simplify it by the way I may have said it, I’m sure everyone else understood what I meant.
Based on what you’re saying, I don’t feel like you know enough about the subject matter to be forming such strong opinions.
You have no idea what went wrong yet seem confident what made things break. You are, simply put, hopelessly clueless, as evidenced by how you arbitrarily combine distros, desktops, and window managers when describing your issues. A more astute user would account for such obvious variables before jumping to conclusions.
Wayland is not responsible for the issues you’re describing. You’re just woefully stubborn and unwilling to be wrong. It’s fucking embarrassing and if you weren’t completely mentally spent, you would feel shame.