it is anything but easy to read if your entire file does not fit on a single screen.

but in games, triple buffering is the norm

new features are fine. But first and foremost, is not breaking existing apps, or committing to porting them yourself. So if desktop apps need to do xyz, then wayland needs to support doing xyz. period. No ‘but that’s insecure’, no ‘but why would you want to do that’ (for setting a window icon or positioning the window ffs). Support existing applications. I’m not saying it should support x protocols. But it should offer replacement features for existing apps to be ported to. And it needs to be wayland. Because it’s already the case that certain functionality is implemented for gnome, or kde, with incompatible apis, to fill in the void left by wayland itself. If I want an app to work as I want it, consistently, everywhere? X, with all its warts, is my only choice.

As an example, the accessibility protocols. They’re good to have. Except they’re opt-in. So incompatible with existing apps. Some apps need to restrict access. They could declare that and make use of additional functionality. But no, choose a default that break everything instead.

The argument that apps just need to be ported also assumes the app is still maintained. Are you willing to do the work yourself if not? Probably not. You’re just the one looking down on people like me for wanting functionality in existing apps to be “not literally impossible to implement”

I do not care about security risks. If something made its way onto my system, I’ve already lost. I just want one implementation of something that gets the job done. And by “gets the job done” I mean it allows us to do things better, not disallow us from even having the option to do things because someone had their tinfoil hat on too tight. Ffs you can’t even set your window icon. I don’t care if kde has implemented that feature. If I use that, I’d be supporting kde, not wayland. It won’t work on other des and so the maintenance burden increases drastically.

“almost” being the key word there.

xwayland cannot ever be removed, because wayland, by design, will not have enough functionality to replace it. So one can either support X desktop environments with their own individual bugs, or one X implementation that has the needed features and works consistently for all DEs

because for most of them, there is nothing to port them to. Wayland is incomplete… by design.

I usually just ask them to back that assertion up by running “pacman -Rcs xwayland” (or their package manager’s equivalent).

None have taken me up on my request, and they immediately switch to blaming the apps for it, even though some literally cannot be ported.

ansible claims to be lots of things it’s not. It’s supposed to be idempotent. It’s not, you can execute arbitrary scripts. You don’t need an agent on the machines… but it might just decide to stop supporting your version of python one day. It’s okayish for setting up some machines, but absolutely sucks for maintaining them.

yes

this will not help op in any way with what they need. Which is to recover data already lost.

So in other words, thank you, Captain Hindsight!

if they don’t have access to install keyloggers then you don’t need to protect yourself from them.

except the portal keeps popping up whenever I touch my controller, and the remember option does not work. It pops up in the foreground anytime I even accidentallytouch my contoller’s touchpad. In home streaming is basically impossible for me rn.

No, they are not. If someone has enough access to install a keylogger, then they can just grant permission to themselves. This is mostly security theater, trying to turn desktops into phones.

i switched to porkbun from godaddy specifically because of this.

the shortcuts usually are associated with a button or menu item that could be pressed.

a configurable set of commands with a keyboard shortcut attached to them.

so… you invented hotkeys?

including other water molecules?

but it didn’t do jack shit to help me believe that. Because they did not say that that was the goal. So there was no credibility to affect in the first place.

Also, your argument does not make sense anyway. As a native language, due to some extra copying needed and some runtime checks that cannot be elided, it is slower than c++. It can be almost as fast, really close, but ever so slightly slower.

Electron is written in c++. A native language. A native language faster than rust (we’re talking about speed not safety here). And yet, it is the canonical example of “bloated and slow”. If you were to rewrite electron in rust, it’d be safer, but also at least just as slow.

So if the editor really is faster, it’s not because the code was written in rust. It’s because the devs are writing better code. That’s why just saying it’s written in rust is useless.