- Joined
- Dec 17, 2019
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
I do agree that X11 is great, though, and it's a shame that with Redhat dropping support it will probably Start to rot, considering they were the ones keeping it alive, IIRC (though I am interested in being proven wrong if otherwise). Openbox is still the most problem free environment I have used ever including with any other OS.
If it ain't broke...I personally wouldn't put a colossal project like X11 on "pause" for 13 years while quietly maintaining what we have, but it is what it is.
True, my software can't work properly on wayland because of this. Also software like DAW (digital audio workstation) cant work properly on wayland since there is a plugin standard for DAW (that works across different software and OS') and they work by creating a window in one process that gets embedded into a window in another process. This is not possible on Wayland and Wayland devs have stated that they dont want to support this, despite this feature actually improving software security, stability and modularity.If it ain't broke...
Wayland will never, by design, reach feature parity with X11.
It's a bit funny to me. At my previous job I had a swedish boss (just like in that series) that also ran kde plasma while everybody else ran gnome/xfce/etc.I was recently re-watching this series and I completely forgot this retarded scene existed:
Let's see Paul Allen's rice.
Isn't Wayland mostly maintained by the same faggots that bought you Gnome and GTK? Explains why shit is so backwards with it.This is not possible on Wayland and Wayland devs have stated that they dont want to support this, despite this feature actually improving software security, stability and modularity.
That's the most horrible thing I can think of. Why would you speak evil into the world?
Don't forget: written in RustThat's the most horrible thing I can think of. Why would you speak evil into the world?
Can't we just compile it straight into the kernel to improve performance?
Not such issues in my case, really the only issue I had with this GPU since I got it almost a year ago, ignoring mess with ROCM but I've got a workaround for it.My cursor has always frozen with my amd gpu. The only fix I found was to enable software cursor. Software cursor also seems to have lower latency for whatever reason, even lower than on windows.
Just watch with dmesg for amdgpu errors, I can reliably reproduce it by scrolling in ksystemlog, which is funny because I'll get fresh errors immediately.FWIW: Fedora 42, using GNOME 48, X11 session, and tracking the most recent kernels. GNOME Shell chugs ever so slightly but it’s highly noticeable, there’s a disconnect between when I click something vs when the window pops up. I am an AMDGPU user too; what logs, greps, or full dmesg outputs do I need to see if it is indeed this regression?
[drm] *ERROR* dc_dmub_srv_log_diagnostic_data: DMCUB error - collecting diagnostic data
Nah, I'm tracking LTS kernels because of ZFS, besides I learned my lesson years ago that unless you are running hardware released recently it's are just asking for regressions.You could also just try the mainline kernel. And see if it's fine there. That should be around 6.15.0 now. Probably depending on your distro.
You can actually have proper per-monitor fractional HiDPI on x11 if you use qt. The issue people see with hidpi on x11 is because gtk doesn't support fractional scaling and neither does it on wayland. The only thing missing in x11 is for somebody to decide on a name for the scaling option so that different ui toolkits can have a unified way of setting scaling. X11 supports per-monitor properties without changing anything in x11 (with xrandr) so no code has to be changed to do this.Isn't Wayland mostly maintained by the same faggots that bought you Gnome and GTK? Explains why shit is so backwards with it.
Only been with the KDE devs focusing on it in the last few years that shit is finally getting done after 20 years of being stuck in development hell.
Still not as good as X, but I do use it on my HiDPI laptop since Wayland is a better experience with that (still absolute garbage, its just usable garbage now). Having only 1 global scaling option was the big dealbreaker for me personally.
X will never die though, at the very least it will last much longer then all Wayland loving troons.
No. There are a lot of people in all parts of the Linux development community that are taking part of it.Isn't Wayland mostly maintained by the same faggots that bought you Gnome and GTK? Explains why shit is so backwards with it.
.
Well I have been proven wrong. I gave xrandr moon runes a go last time I tried HiDPI on X but I couldn't get it working right.You can actually have proper per-monitor fractional HiDPI on x11 if you use qt. The issue people see with hidpi on x11 is because gtk doesn't support fractional scaling and neither does it on wayland. The only thing missing in x11 is for somebody to decide on a name for the scaling option so that different ui toolkits can have a unified way of setting scaling. X11 supports per-monitor properties without changing anything in x11 (with xrandr) so no code has to be changed to do this.
Here is an example of x11 with per-monitor scaling:
The gnome people, at least now. Seem to only fuck shit up when everyone else is trying to move forward with something.
XFCE sees little to no "attention" by busybodies trying to "fix" it, that's why it's still good.Wayland has been in development for how many years now? The problem with Linux tards if you can have 1,000 working on a project, and 1,000 of them will have different ideas, code, crap, and argue constantly among themselves.
And once the linux tards finally figure something out, they branch out to break it again. Take a look at Pop OS, it was fine under Gnome, now they have been fucking around with COSMIC desktop for endless years now and it still doesn't work properly and still in alpha stage.
Google did Linux right. You make it not open source which removes all the tards from it, develop it in private under corporate leadership, and then only release shit when it works right.
Exactly. People who use Gnome rely on extensions and every time a new Gnome version comes out, say 47 to 48, it fucks up most of the extensions and by the time those maintainers catch up, a new Gnome comes out. No wonder there is so many dead or non-compatible extensions out there now, people just give up. XFCE does it right, why change what works?
It doesn't have to be proprietary to get work done. You just shouldn't do it the way the wayland people have. There are plenty of completely open source projects that do fine. And there are a lot of ways to do it. Like the BDFL method. Though you don't even need to do that.Google did Linux right. You make it not open source which removes all the tards from it, develop it in private under corporate leadership, and then only release shit when it works right.
Yeah, the real problem is often not due to having too many cooks in the kitchen; it’s when some of them wield too much influence over a project. For example, when a few developers arbitrarily decide, “Nah, we don’t want to add that,” and dismiss features for sometimes vague reasons. These are things people actually want to merge and are willing to maintain. I think Dunning-Kruger egos are a problem w/ development in general today. Esp now with the infestation of trannies and jeets into the space.But having a big project, like wayland, That needs to work for everything under the linux umbrella, if it's going to be what everything runs their graphical session on. Means a lot of people, with a lot of competing interests, want to have their say in how things get done. Which things are important, which don't need to be there. And it's made the project a shit show, as far as the direction of development goes.
Use case for X11?For example, when a few developers arbitrarily decide, “Nah, we don’t want to add that,” and dismiss features for sometimes vague reasons.