I’m using gnome rn and it doesn’t crash much anymore. When I used xorg, there’d be crashes that brought down the entire desktop (or the computer as a whole) too. Also, generally every time I have a crash now it’s from using xwayland to play a game and having certain extensions enabled at the same time (although those issues seem to have disappeared recently too). All the other issues I either don’t care about or are supported with some extra work. For gnome, some of the issues are just because they have a phobia of exposing settings and you need to use stuff like dconf to deal with it.
Jesus what joke of an implementation, it’s the anti theist of Linux. Everyone got fooled and allowed GUI developers implement the rendering backend…
As you mentioned earlier, it’s a protocol. Implementation issues are due to how gnome/kde/whatever implemented their compositors. I think it’s pretty much standard for Linux given that stuff like systemd and flatpak exist. If you want to use something more traditional unix-y, maybe you should use a bsd or solaris derivative or something.
I think it’s pretty much standard for Linux given that stuff like systemd and flatpak exist. If you want to use something more traditional unix-y, maybe you should use a bsd or solaris derivative or something.
That’s a pretty toxic take, much in the way like Windows does things.
I mean the person I’m responding to seems to want a traditional Unix experience given how they’re talking (and given they use suckless software). Linux generally isn’t that, and it never really has been (or at least hasn’t for many years). If you want something more traditional, there are a bunch of available options like the BSDs. If you insist on using Linux, you can use distros that don’t use Wayland, systemd, flatpak, etc., but the support for them is lower, and if you need to use something that isn’t packaged for example you’ll need to deal with getting it working with e.g. systemd on your own. A bunch of software makes assumptions that stuff like systemd is now included if you use Linux. I’m currently using a distro without systemd and am seriously considering swapping back to my old one because it’s such a hassle.
Admitedly, i’m currently in a “take a step back” phase and like to see software breaking. It’s healthy for the linux ecosystem if things break.
And in software that is a hassle (usually Gnomes on a not-Gnome environment) either the software itself is really good and somebody made a patch or packaged a old working version already. Or i look for something simpler to do the same.
I still use x11 with suckless dwm, but for work I’m forced to use Ubuntu 25.10 gnome shit. It’s a sad state. Gnome owns all the process you start via gnome, that is why if gnome dies all the child process es dies as well, genius. Because the buggy mess, doesn’t critical errors and never will have…
I don’t know how you use gnome, if it doesn’t crash for you, fine, good. But that’s not my reality, it can crash because I open the laptop screen while being on an external monitor. It can crash because I’m screen sharing, it can crash because some software I used froze, it can crash for random reason (doesn’t happen often, but still annoying).
I’m using gnome rn and it doesn’t crash much anymore. When I used xorg, there’d be crashes that brought down the entire desktop (or the computer as a whole) too. Also, generally every time I have a crash now it’s from using xwayland to play a game and having certain extensions enabled at the same time (although those issues seem to have disappeared recently too). All the other issues I either don’t care about or are supported with some extra work. For gnome, some of the issues are just because they have a phobia of exposing settings and you need to use stuff like dconf to deal with it.
As you mentioned earlier, it’s a protocol. Implementation issues are due to how gnome/kde/whatever implemented their compositors. I think it’s pretty much standard for Linux given that stuff like systemd and flatpak exist. If you want to use something more traditional unix-y, maybe you should use a bsd or solaris derivative or something.
That’s a pretty toxic take, much in the way like Windows does things.
I mean the person I’m responding to seems to want a traditional Unix experience given how they’re talking (and given they use suckless software). Linux generally isn’t that, and it never really has been (or at least hasn’t for many years). If you want something more traditional, there are a bunch of available options like the BSDs. If you insist on using Linux, you can use distros that don’t use Wayland, systemd, flatpak, etc., but the support for them is lower, and if you need to use something that isn’t packaged for example you’ll need to deal with getting it working with e.g. systemd on your own. A bunch of software makes assumptions that stuff like systemd is now included if you use Linux. I’m currently using a distro without systemd and am seriously considering swapping back to my old one because it’s such a hassle.
Admitedly, i’m currently in a “take a step back” phase and like to see software breaking. It’s healthy for the linux ecosystem if things break.
And in software that is a hassle (usually Gnomes on a not-Gnome environment) either the software itself is really good and somebody made a patch or packaged a old working version already. Or i look for something simpler to do the same.
I still use x11 with suckless dwm, but for work I’m forced to use Ubuntu 25.10 gnome shit. It’s a sad state. Gnome owns all the process you start via gnome, that is why if gnome dies all the child process es dies as well, genius. Because the buggy mess, doesn’t critical errors and never will have…
I don’t know how you use gnome, if it doesn’t crash for you, fine, good. But that’s not my reality, it can crash because I open the laptop screen while being on an external monitor. It can crash because I’m screen sharing, it can crash because some software I used froze, it can crash for random reason (doesn’t happen often, but still annoying).
I can tell from the way you write, no need to mention it.
No worries, I would like you to have it in written statement.