Earlier quoted context omitted.
There was not really for system utilities. Apps, sure, but not system utilities.
What do you refer to as system utilities? All the stuff now subsumed by SystemD?
Preparing for KDE Plasma's Last X11-Supported Release
341–350 of 392 posts
Re: Preparing for KDE Plasma's Last X11-Supported Release
#342Earlier quoted context omitted.
Turn off the web browser feature that allows JS in an advertisement in a background tab to globally grab your input.
Sure, browsers had three decades of adversarial testing to evolve into sandboxes, but what are you going to do in case of something like the xz backdoor in a desktop application? It's no longer a hypothetical in 2020s.
Re: Preparing for KDE Plasma's Last X11-Supported Release
#343But I have to use wayland because I've got nvidia and the force composition vsync hack is just too slow to game with reliably.
Re: Preparing for KDE Plasma's Last X11-Supported Release
#344Earlier quoted context omitted.
Yes, exactly. This security paranoia makes the devs' lives much more complicated. I have seen many apps turning off advanced features, such as screen color pickers. Automatation tools can be broken. Apps cant know their window positions, etc. You can see countless dev rants about Wayland and how it's generally unpleasant experience to work with.
Ah so that's why i cant use the chrome devtools color picker to pick colors off graphics editing software. Makes me mad.
Re: Preparing for KDE Plasma's Last X11-Supported Release
#345Earlier quoted context omitted.
Sure, browsers had three decades of adversarial testing to evolve into sandboxes, but what are you going to do in case of something like the xz backdoor in a desktop application? It's no longer a hypothetical in 2020s.
You're going to be hacked. There's no useful middle ground between letting programs modify how your computer works and not letting programs modify how your computer works.
Re: Preparing for KDE Plasma's Last X11-Supported Release
#346Earlier quoted context omitted.
You're going to be hacked. There's no useful middle ground between letting programs modify how your computer works and not letting programs modify how your computer works.
Of course there is: fine-grained access control and attack surface reduction. It's not all or nothing.
Apple apologists keep making the excuse that Apple has to provide no side loading because if there was any single way to do it, all scammers would be making all grandmas do that. They're correct.
Re: Preparing for KDE Plasma's Last X11-Supported Release
#347Earlier quoted context omitted.
When I upgraded from Debian 12 to 13 on my personal laptop running KDE, I knew that the switch from X11 to Wayland would happen and was braced for all kinds of issues, like every other time I tried to switch to Wayland in previous years. Instead, I could tell literally no difference. Multiple desktops works fine, scaling works fine, screen capture works fine, old apps work fine, literally everything works just fine.…
I think I noticed lower latency, more consistent frame pacing (recent-ish improvement in KWin) and a more "solid" feel because everything in a frame is synchronized. On X11, you can have things like border and contents of a window not matching exactly while resizing. An early principle of Wayland was "Every frame is perfect", which is clearly reflected in how e.g. window resizing works.
For example I was a big user of devilspie for placing windows in certain locations, on certain desktops, marking windows as sticky, or marking them as different types of windows.
I am still a heavy user of pidgin (I know I know but I’ve even written my own protocols for it). I really liked being able to place it in a certain position as a certain size, mark it as sticky, put it below anll windows, and mark the buddy list as a utility window. This places in the background, removed borders, and doesn’t include it in alt-tab or window list when you do the expose type of thing. Then I had a global key binding to bring it to the front of all windows or drop it back of all windows.
As far as I know, none of these paradigms even exist in Wayland and I’ve had to deal with less useful options or completely change my interactions which is unfortunate.
Re: Preparing for KDE Plasma's Last X11-Supported Release
#348Earlier quoted context omitted.
More and more Free SW will depend on Systemd (like next gen flatpak). Make something better or adapt.
No, I will use software that respects me instead of software that makes demands of me.
Re: Preparing for KDE Plasma's Last X11-Supported Release
#349Earlier quoted context omitted.
I'm sorry, but are we still going on about this? I love a good debate as much as the next guy, but being able to just have one interface (systemd's) for all services and having a more-or-less consistent language really helps. At this point, it's simply a bit too late. I'm sure in the early days it was still a choice, but when you want prepackaged things, you get systemd.
You could also just use one system (Windows) for everything if you wanted. Some of us decided to use Linux because we want things to work how we want and not how some bigshot decides they should work.
But if you are using software that other people provided to you for free, I think the developers also get a say in how things work. And in case you didn't notice, most open source licenses will tell you that they don't provide any kind of warranty.
Re: Preparing for KDE Plasma's Last X11-Supported Release
#350Earlier quoted context omitted.
Of course there is: fine-grained access control and attack surface reduction. It's not all or nothing.
Do you want to see the dancing bunnies? [Yes] [No] Apple apologists keep making the excuse that Apple has to provide no side loading because if there was any single way to do it, all scammers would be making all grandmas do that. They're correct.