Yes and that's how it's done on Wayland. I don't see any reason why kwin on X11 couldn't do something similar except that you'd have to get all the various programs that want to see the screen to cooperate.

With Wayland, the only way to get an image of the screen is through the compositor through a somewhat well-defined interface (works across several different compositors), so that's what Zoom, OBS, screenshot programs all have to use. But on X11 all the apps just grab screen shots directly from the X server currently. At this stage a standard for X11 just isn't going to happen. Besides that, what would you do if you didn't have a compositor running? Would require fallback code. I just don't see anyone getting real excited about that. Whereas on Wayland these features can be added by the compositor for free as it were, and the screen sharing apps don't have to know anything about it or do anything special.

No, not really. X11 simply has no architecture for that sort of separation, and no way to screen share anything other than what is in the frame buffer.

Oh I see. It's not an option in Dolphin, it's in Plasma settings under Workspace->General behavior.

Very true. Although I hope KDE continues to work equally well on X11 and Wayland. And on other Unix OSes. Perhaps even on Windows. There was a time when I ran KDE on Windows, mostly for kicks. Alternate shells for Windows have disappeared and been banished by MS, sadly.

Regarding Wayland, it is worth noting that one of the features in the summary---not showing certain windows when screen sharing---is a wayland-only feature. X11 simply does not have a way to easily do it.

KDE was really the first real DE for Linux, long before Gnome was a thing. Had it not been for the Qt license issue back then, GTK and Gnome would never have been created. Imagine a world without Gnome and where the GIMP was made from Qt. Some would like it and others probably shiver.

Back in 1998 I was struggling to learn Red Hat 5.1 with fvwm2, coming from an MS/DOS and Windows 95 background. KDE 1.0 came out and I downloaded a bunch of RPMs at the uni lab on a zip disk. I installed it and that changed Linux for me in an instant. I hated the single click thing, but other than that it really made Linux accessible to me. So I owe KDE a lot. After about 20 years in the Gnome 1/2/Mate Desktop world, I've come back to KDE Plasma 6 and quite like it. It does exactly what I want and can be tweaked and configured to suit my needs.

I've read there is a config option to make "move" the default like it is on other OS's, but I can't find it. Using shift and ctrl does work like other OS's and avoids the popup menu. But yeah it's awkward, so I'm glad I just use Caja and avoid dolphin altogether.

It still did as of 6.5.5. But the nice thing about KDE is you can use whatever parts of it you want. I'm currently using Caja as the file manager inside of KDE. No particular reason, but it works fine and I think it looks a lot better than Dolphin.

Axis of Awesome is guilty of copyright infringement on a massive scale. https://www.youtube.com/watch?...

Many reasons, including better support for HiDPI.

That said, there is full X server called Wayback which essentially uses Wayland as a graphics driver. Kind of neat project.

Blasphemy! :)

Of course you could just set EDITOR...

vim has always used cursor keys as long as I've used it (at least 30 years), unless something was really messed up with the terminal settings.

I find programming without vim key bindings frustrating. The basics are what I use the most. change word(s), replace character, yank line(s), delete line(s), paste before, paste after, insert, append, indent block. Even something like append is so powerful. And the best part is the repeat command turns what you just did into a mini macro. So it's really fast to do simple changes (like inserting text at the beginning of a line) down through dozens of lines. I often combine the repeat command with the search command, making ad-hoc refactoring super fast. And it's all muscle memory.

But mostly my comment about NppVim was tongue in cheek since my position is an editor without vim key bindings cannot do what vim can do!

No one has used TCP/IP ports to forward X for decades now. X.org doesn't even listen on those ports anymore. It's all done with unix sockets and shared memory now because of things like OpenGL. It's also because of the needs of modern apps and hardware acceleration that 99% of X11 isn't even used anymore and modern GTK or Qt apps use X11 more like how rdp works, pushing bitmaps across (client-side rendering).

As for what Wayland apparently forces you to do, I am not sure if you're simply misinformed or lying. I ssh -X all the time from KDE on Wayland to forward remote X11 apps. It just works, like it always has. Every app on my distro that can run natively on wayland also has an X11 backend that works for forwarding. As long as the toolkits support X11, this will continue to function. My only problem with Xwayland is it's not easy to deal with some X11 apps that aren't hidpi aware at the same time as X11 apps that are hidpi aware. I really need to be able to run two instances of Xwayland, one for hidpi apps and one where the apps need to be scaled by Xwayland.

Anyway you could sit down at my KDE wayland desktop and if I didn't tell you it was Wayland you'd never know since it everything including ssh -X works as you have always expected it would. Except that things like having a 4K hidpi main monitor and a 1080P second monitor would work, whereas on X11, you cannot have different scale factors on multi monitors.

I think you miss the point of having vim key bindings. To me an editor is unusable without them, or at least a lot less usable. Obviously I can get by with a "normal" editor, but it really hurts my efficiency. Even something as simple as yanking or replacing a word (or words) is painful in a conventional editor compared to the speed and ease with which I can do it with vim-like commands. (You want me to shift arrow key and highlight like an animal when a couple of keystrokes can do it?) And the ability to create ad-hoc macros just by using the vim repeat mechanism is unmatched in a "normal" editor.

But the main benefit is with VI bindings I no longer end up with random ":w," "gg", "GG", etc in my text! In fact a spurious "dd" found its way into this html edit box just now. Buggy software.;)

My only real complaint about VI key bindings is that the undo key is too close to the yank and insert keys, so I often end up hitting the wrong one. And also VI key bindings don't work that well on dvorak keyboards for me.

X11 app forwarding over ssh works just as well when using modern Wayland desktop as it always did, thanks to Xwayland which isn't going away. I use it very frequently. In fact Xwayland is a full X server implementation based on x.org. It runs transparently and automatically on the major desktop environments such as Gnome and KDE. And it will continue to work as long as the applications you run and the toolkits they are built with continue to have an X11 backend.

For Qt this is likely to be the case nearly indefinitely, or maybe until waypipe is mature.

The only worrisome thing is that the Gnome folks are wanting to remove X11 support from GTK+ which will definitely break ssh forwarding for those apps. But I don't use Gnome anymore and I use fewer GTK apps all the time.