this is unacceptable , i installed arch and got plasma 6 instead of plasma 5 Now i will have to deal with the bugs crawling on it
and its freaking idle ram usage is 1Gb thank god i have 16gb ram or else i was dead
now i have to rice this kde machine
I’m guessing the higher RAM usage is due to Wayland and not Plasma 6, or is it the other way around? KDE has always been known for being much lighter than Gnome, almost as much as XFCE, so this is a concern.
I know Wayland is supposed to be the future and technically it does sound like a better architecture, but is it actually better w.r.t.performance? the only thing measurably better seems to be security, but in practice all that does is break a bunch of apps that peope depend on. I dont think there are exploits for X11’s supposedly weaker security?
depending i think… from what i can see on low spec machines wayland feels better and smoother compared to X11 be it kde or cinnamon… no tearing per example…
I have what many would call low spec, its a Thinkpad T430, 10+ years old. Is tearing supposed to be noticeable when I move windows? because I’ve never really noticed it.
No, it doesn’t. It sounds like a completely defective idea.
Doubtful. I’d like to see some of those measurements.
Unless you consider removing features to be a security improvement. In that case, turn of your computer and never power it on again. There is nothing more secure than that.
Well, I agree with you, but it begs the qn - what is the point of Wayland? its been over a decade, maybe 15years?, still nowhere complete, not to mention lacking features. Not a complete solution, it requires you to implement a lot of the protocol yourself, ensuring things will never be compatible.
the whole idea was to be a more modern and secure alternative, that was decades ago.
Meanwhile Windows and MacOS have extremely efficient, robust display engines and desktop compositors. Wayland/X11 can’t even match simple remoting - just look at what RDP has been doing for decades and how its so much more efficient because it doesnt need to send bitmaps.
ok this is getting off topic. I want to ask - did Fedora face same issues with adoption of Wayland as KDE is?
I may be being hopeful, but I HOPE that as we transition to Wayland (finally), progress will be made by virtue of resources being focused on solving the problems with Wayland protocols vs ‘Well, it’ll never get off the ground’.
A shift is sometimes necessary to move forward.
Maybe because its hard to make all a ecosystem to move toward the same direction? Real progression started only in 2019/2020.
Protocols are there to define how everything should work, and to do so in a modular way. If each implementation follows a guideline, I find it hard to understand why “ensuring things will never be compatible”. It’s just the opposite, you have to see it as an API, with ways of interacting with x things and this will work on every DE that support it. xdg-portals are also great in this aspect.
The client asks for the list of features that the wayland compositor supports, so as a dev you know what you can and can’t do at runtime.
Windows display engine is not that great IMO. Any gamer who has used Windows with an HDR screen knows exactly what I’m talking about. And I can’t count the number of times I’ve seen the file explorer stop responding and taking off with it explorer.exe
Most likely some missing features would be implemented at some point in the future.
Everyone is allowed to implement their own compositor + custom protocol + clients, they are independent of Kwin control.
Multiple compositors (for example Kwin, your own keylogger compositor and game compositor, …) can run in parallel on root background.
Wayland’s goal is microservice architecture.
Xorg is monolithic architecture like All in One.
Two things:
- Xorg is really old and bloated and a total mess, it is getting really difficult to maintain it, and to add new features to it.
- Wayland exists. Unfortunately.
Wayland is a product of people who got traumatised by working on Xorg. It’s a damaged concept made by damaged people. It’s a total overcompensation for the shortcomings of Xorg.
In the ideal universe, Xorg would be rewritten from scratch. In this universe, we got Wayland. It sucks. Fortunately, Xorg is not going away any time soon, so there is still hope for something better to emerge before it kicks the bucket for good.
X12 maybe ?
https://www.x.org/wiki/Development/X12/
We have a fundamental Wayland vs X11 conversation? I’m shocked. Shocked!
![]()
You can be certain that as soon as the word “wayland” is written somewhere, there will be a frog croaking about it.
![]()
Write GNOME-Wayland and there you will have the whole Circus ![]()
Well X11 wasn’t built in a decade or 2 rether almost 4!(June 1984; 39 years ago, source wiki. ) then again the last 10 or so years development has been dead.
I think Wayland is the future!.. Unless something else comes along that is better.
But anyway to come back to the topic, KDE Plasma 6 feels great!
I thought X12 was a crypto thing: https://github.com/x12project/x12-core ![]()
![]()
totally legit to yea take it as the only possible solution … welcome to the age of “nuts”
Then you’ll have more problems. ![]()
isn’t this the same argument that was advanced eons ago when Hurd was announced - a microservice based Linux kernel, and there have been many iterations since, and none of them have had any mass adoption or completion compared to monolithic kernel?
of course in reality the kernel itself is also modular, it just doesn’t have multiple independent binaries in a different process space the way a true microservice architecture would work