For a user: In Wayland programs are supposed to draw their own title bar. Java aplications and old applications must use a backwards compatibility layer that can cause flicker and bad font rendering. The terminology is different (compositor = window manager). Some niche new programs may only run on Wayland. Wayland hasn’t been adopted by BSD (AFAIK).
For a programners: Wayland has more modern, tidy code, but not all toolkits support it natively and few are easy. If you code exclusively for Wayland, a lot of users won’t use your program at the moment.
In Linux terminals, you probably could have pressed Alt+F2 or Ctrl+Alt+F2 (F2 could be other F-keys) and log in on a second terminal to recover (by reading the manual or killing it). Also, if bash already had job control back then Ctrl+Z would have suspended vi/vim to the background.
I’m writing this, so people try it and maybe remember it, if they get stuck in some program. Doesn’t have to be vi. Maybe you just launched a long dd command and don’t want to end it, but want to look something up. These hints may help then.
Lemmy really needs something like topics, categories or tags you can opt-in or -out of. There are just too many communities to subscribe one by one and if I browse everything theres so much super boring niche stuff, like some Go library releasing version 0.02-beta. I mean that’s nice for those 5 Go programmers waiting for that, i guess, but they are probably subscribed to it anyway.
Idk what “container” means in this case, but gimp is only like 80 MB + some dependencies you probably already have installed. Do you mean RAM or HD memory? In any case it should be much less than 64 GB.
The best way used to be XPRA. You can also tunnel it thru SSH, but not necessary in a trusted LAN. XPRA is like a per application display proxy that keeps an app running even if the connection is interrupted and enables reconnects as well as transfers of Xclient windows to other Xservers, i.e. you can transfer the remote window from your notebook to your workstation Xserver whithout having to restart the app.
As long as you do not use root privileges (indicated by sudo or that password promt pkexec) you cannot destroy the system in a way that can’t be fixed by deleting a few files in the users home directory.