Except when X doesn’t fucking work ™ and hasn’t properly worked in literal decades. I don’t think I’ve ever managed to get rid of horizontal tearing with X. Calling X feature complete is pretty funny, but it isn’t. So many things were never fully implemented, because it’s just an impossible amount of work or would require some major rearchitecting. You don’t have to deal with updates because literally no one wants to develop it any further or even maintain it. The devs have moved on to Wayland or other things.
It’s fine if it works for you, but I’m getting tired of Linux conservatives projecting their own experiences on everyone else and declaring Wayland as “not ready yet” and handwaving all of X’s obvious problems away because they’re used to dealing with them. I’ve used Wayland as a default for all my machines for years. After a rough beginning where major features were still in development, now it works. XWayland works. Native Wayland apps work. I don’t have tearing anymore. I’m not going to pretend that that’s the universal experience, but a lot of people are using it just fine right now.
i switched to i3wm and picom, recently, initially had issues with tearing, but honestly, i just haven’t seen tearing recently, and i’m not sure why.
It’s fine if it works for you, but I’m getting tired of Linux conservatives projecting their own experiences on everyone else and declaring Wayland as “not ready yet” and handwaving all of X’s obvious problems away because they’re used to dealing with them.
valid opinion i guess, but i just stated the reason why i’m waiting a few years until moving to wayland, if i were a linux conservative i would refuse to move off of X lmao.
It’d be nice to use wayland, but from what i’ve heard and what i’ve seen it sounds like it’s going to be equally as annoying as X is, especially more so because i’m currently using nvidia, and wayland doesn’t seem to support nvidia as well as X does, just due to development focus. Currently i just don’t think the CBA is going to be significantly net positive enough to rip up my entire current install, transition from i3wm, to another one, and then start using/learning wayland, just yet.
Like yes major releases and distros are moving to wayland now, that just means they find it stable enough to start doing development on it. I’ll wait a bit and then later move over once things settle down. I have years of experience using X, and significant familiarity with it. I have none with wayland, i’d simply prefer to wait a bit.
wayland doesn’t seem to support nvidia as well as X does, just due to development focus
Ymmv with Nvidia, but that has nothing to do with development focus and everything to do with Nvidia’s refusal to use the same interfaces Intel and AMD use. Most of the way Nvidia works or doesn’t work with X or Wayland is down to Nvidia’s driver stack. Personally I’ve not had much positive experiences with Nvidia on X.
Like yes major releases and distros are moving to wayland now, that just means they find it stable enough to start doing development on it.
That happened literal years ago. The reason you’re only noticing now, might be because KDE has gotten their Wayland implementation to a reasonably stable point. Gnome has supported Wayland for some time now and other DEs probably don’t have the resources to move on from X. I don’t see the distros that are only switching over now as major contributors to any development specific to Wayland.
I don’t take issue with your preferences. Maybe you’re better off with X for now, that’s fine, but you make it sound like Wayland is just full of issues and has barely even entered some kind of pre-release state for software masochists.
Ymmv with Nvidia, but that has nothing to do with development focus and everything to do with Nvidia’s refusal to use the same interfaces Intel and AMD use. Most of the way Nvidia works or doesn’t work with X or Wayland is down to Nvidia’s driver stack. Personally I’ve not had much positive experiences with Nvidia on X.
that’s what i mean, i don’t blame wayland for it lol. I wouldn’t want to develop for nvidia on wayland either. If nvidia was open and accessible, someone somewhere, would be working on it right now, it’s just how things are.
That happened literal years ago.
it’s possible that i missed a few i’ve only been involved for about 4-5 years so far. I don’t know anything about gnome personally because i don’t use it, but it doesn’t surprise me either tbh. I know about KDE because i used it, i know about fedora because i know people who have used it. I feel like i’ve seen more talk about wayland as of recent, but that’s probably irrelevant lol.
I don’t see the distros that are only switching over now as major contributors to any development specific to Wayland.
it’s not the distros and their devs, it’s the users and their unique hardware configs. More data makes a more reliable and usable system.
I don’t take issue with your preferences. Maybe you’re better off with X for now, that’s fine, but you make it sound like Wayland is just full of issues and has barely even entered some kind of pre-release state for software masochists.
that’s not what i intended, i just said it’s the small issues that appear, and disappear with every few updates, that i don’t want to be dealing with, that’s why i no longer use KDE. I prefer my system to be a relatively consistent level of “broken” most of the time.
A lot of people don’t have significant issues with that, i believe the previous poster was rather annoyed by them, i imagine they’ll get better soon, but there will likely be hundreds, if not thousands of bugs like this, dependent on specific hardware configurations, that will crop up shortly. And then just randomly disappear, or morph into other bugs, this is the QOL hell part of development.
X is rather stable on virtue of not being updated anymore, so those aren’t really significant concerns.
Except when X doesn’t fucking work ™ and hasn’t properly worked in literal decades. I don’t think I’ve ever managed to get rid of horizontal tearing with X. Calling X feature complete is pretty funny, but it isn’t. So many things were never fully implemented, because it’s just an impossible amount of work or would require some major rearchitecting. You don’t have to deal with updates because literally no one wants to develop it any further or even maintain it. The devs have moved on to Wayland or other things.
It’s fine if it works for you, but I’m getting tired of Linux conservatives projecting their own experiences on everyone else and declaring Wayland as “not ready yet” and handwaving all of X’s obvious problems away because they’re used to dealing with them. I’ve used Wayland as a default for all my machines for years. After a rough beginning where major features were still in development, now it works. XWayland works. Native Wayland apps work. I don’t have tearing anymore. I’m not going to pretend that that’s the universal experience, but a lot of people are using it just fine right now.
i switched to i3wm and picom, recently, initially had issues with tearing, but honestly, i just haven’t seen tearing recently, and i’m not sure why.
valid opinion i guess, but i just stated the reason why i’m waiting a few years until moving to wayland, if i were a linux conservative i would refuse to move off of X lmao.
It’d be nice to use wayland, but from what i’ve heard and what i’ve seen it sounds like it’s going to be equally as annoying as X is, especially more so because i’m currently using nvidia, and wayland doesn’t seem to support nvidia as well as X does, just due to development focus. Currently i just don’t think the CBA is going to be significantly net positive enough to rip up my entire current install, transition from i3wm, to another one, and then start using/learning wayland, just yet.
Like yes major releases and distros are moving to wayland now, that just means they find it stable enough to start doing development on it. I’ll wait a bit and then later move over once things settle down. I have years of experience using X, and significant familiarity with it. I have none with wayland, i’d simply prefer to wait a bit.
Ymmv with Nvidia, but that has nothing to do with development focus and everything to do with Nvidia’s refusal to use the same interfaces Intel and AMD use. Most of the way Nvidia works or doesn’t work with X or Wayland is down to Nvidia’s driver stack. Personally I’ve not had much positive experiences with Nvidia on X.
That happened literal years ago. The reason you’re only noticing now, might be because KDE has gotten their Wayland implementation to a reasonably stable point. Gnome has supported Wayland for some time now and other DEs probably don’t have the resources to move on from X. I don’t see the distros that are only switching over now as major contributors to any development specific to Wayland.
I don’t take issue with your preferences. Maybe you’re better off with X for now, that’s fine, but you make it sound like Wayland is just full of issues and has barely even entered some kind of pre-release state for software masochists.
that’s what i mean, i don’t blame wayland for it lol. I wouldn’t want to develop for nvidia on wayland either. If nvidia was open and accessible, someone somewhere, would be working on it right now, it’s just how things are.
it’s possible that i missed a few i’ve only been involved for about 4-5 years so far. I don’t know anything about gnome personally because i don’t use it, but it doesn’t surprise me either tbh. I know about KDE because i used it, i know about fedora because i know people who have used it. I feel like i’ve seen more talk about wayland as of recent, but that’s probably irrelevant lol.
it’s not the distros and their devs, it’s the users and their unique hardware configs. More data makes a more reliable and usable system.
that’s not what i intended, i just said it’s the small issues that appear, and disappear with every few updates, that i don’t want to be dealing with, that’s why i no longer use KDE. I prefer my system to be a relatively consistent level of “broken” most of the time.
A lot of people don’t have significant issues with that, i believe the previous poster was rather annoyed by them, i imagine they’ll get better soon, but there will likely be hundreds, if not thousands of bugs like this, dependent on specific hardware configurations, that will crop up shortly. And then just randomly disappear, or morph into other bugs, this is the QOL hell part of development.
X is rather stable on virtue of not being updated anymore, so those aren’t really significant concerns.