301–310 of 335 posts
Earlier quoted context omitted.
That's always what's missing from these threads. Wayland is boring actually. It just works. KDE, Sway, Niri, whatever, are all good. I don't know what to do. The outpouring of negative energies are so severe. But I think it's so incredibly un-representative, is so misleading. The silent majority problem is so real. Come to the better place.
How do I run a GUI application over ssh? This is what’s keeping me from switching.
Earlier quoted context omitted.
That's one of Wayland's other major faults IMO
It is a major improvement: many real life compositor implementations, discover dynamically the features of the compositor, some will have a remote desktop expensive feature.
Earlier quoted context omitted.
I prefer Wayland, as I feel Wayland's performance is much smoother than Xorg. Though, I have no use for VRR, and I hate the slight lag that is introduced due to font scaling, so I do not use it either. But, I am stuck on Xorg only because of one app that I have to use to work. > My guess is that we'll only start seeing Wayland adoption when distributions start forcing it or making it a strong default, like what happe…
This is the real reason to make the wayland switch. It doesn't really matter if you like or dislike wayland, the major DE have decided they don't like X11 and they are making the switch to wayland. X11 code is actively being removed from these desktop environments. If you want to use X11, you can either stay on an old unmaintained DE or switch to a smaller one that supports X11. But you should realize that with wayla…
It reminds me of things like the pack-in software you get with Windows. It's convenient because it all comes in one place and more or less works together, but not much of it is particularly best-of-breed.
I guess they've sucked a lot of air out of some niches though-- I suspect a lot of utilities for things like system configuration and file management have turned into parts of the desktop environment rather than standalone tools.
Earlier quoted context omitted.
There's no obvious reason for an end used to switch to Wayland if there isn't any particular problems with their current setup, the main improvements come down to things X11 never supported particularly well and are unlikely to be used in many existing X11 setups. My big use case that Wayland enabled was being able to dock my laptop and seamlessly switching apps between displays with different scale factors. And as a…
> having to maintain both X11 and Wayland support forever everywhere I don't get why X11 shouldn't work forever. It works today. As you said, there's no obvious reason for an end user to switch to Wayland if there isn't any particular problems with their current setup. "Because it's modern" and "Because it's outdated" just aren't compelling reasons for anyone besides software developers. And "because we're going to d…
Sure, assuming nothing else changes around it maybe. It'll work in the sense retrocomputing works.
However, the people who used to maintain Xorg are the ones who created Wayland. Xorg is largely neglected now, it still works mostly by luck.
Earlier quoted context omitted.
I am talking about window management. Window management is about controling windows, windows managers should not care about how windows are rendered.
1. Nobody else is talking about managing windows as a user. They’re talking about the system that manages windows for drawing and interaction. 2. You’re provably wrong even if someone followed your description because you can kill the dock or explorer process and still be able to switch between windows and move them around. Killing explorer is a little more heavy handed than killing the dock but it doesn’t take down…
While you can move, resize, minimize, maximize, and switch between windows without Explorer running, other window management features are limited or nonfunctional without it:
1. Explorer is responsible for the taskbar, and thus the only useful way to view minimized windows.
2. Alt+Tab still switches between windows without Explorer, but the window switching UI does not appear.
3. Virtual desktops still exist without Explorer, but there's no obvious way to switch between or otherwise interact with them.
4. Snapped windows retain their positions without Explorer, but window snapping functionality is not available, and resizing snapped windows does not resize adjacent windows as it normally does.
5. Without Explorer, desktop backgrounds and desktop icons do not appear.
5. Explorer is responsible for handling many system level keyboard shortcuts, including shortcuts for features not obviously related to Explorer or missing window management functionality (e.g., game bar, snipping tool, emoji panel).
Earlier quoted context omitted.
The beauty with Free Software and Linux distros is that "they" don't have to do it, anyone who wants to (including you!) can do it.
In theory. In practice, every app is designed for X11 or Wayland, building your own means you need to follow what most people use anyway if you want to have any working app on your system, or rewrite every app yourself
Earlier quoted context omitted.
Taking the proposition as true, what goal does Redhat have in "forcing wayland on users"? I am asking this in good faith, I literally naively do not understand what the "bad" bit is. Like, ok, its 2030 and X11 is dead, no one works on it anymore and 90% of Linux users use Wayland, what did they gain? I know they did employ Pottering but not anymore, and AFAIK they contribute a non-trivial amount of code up stream to,…
Redhat gains at least a few things... - Maintaining X requires a lot of time, expertise and cost, it's a hard codebase to work with, deprecating X saves them money - Wayland is simpler and achieves greater security by eliminating features of the desktop that most users value, but perhaps Redhat's clients in security-conscious fields like healthcare, finance and government are willing to live without So I suspect it c…
Earlier quoted context omitted.
I am the same, now. But I did have it working previously on Nvidia and it was good enough. I’ve also used the TILE patch at work and that seemed pretty good on the 5k screens they have there. I switched to get support for different scaling on different outputs and I have gone back.
The right way to handle high DPI is at the GUI toolkit level. Scaling in the compositor is just a dirty fix for legacy apps.
Earlier quoted context omitted.
It is a major improvement: many real life compositor implementations, discover dynamically the features of the compositor, some will have a remote desktop expensive feature.
I really struggle to believe that remote desktop is expensive to implement/run. And no, this isn't an improvement: It used to be that everyone used Xorg, so all desktops had largely the same features. There was, for example, a way to set keyboard layout that always worked (setxkbmap), and it always worked. Now there are endless different compositors, and they all have different features. Do you want to try a new opti…
If I am not too mistaken there are several "remote desktop network protocols", maybe the dev teams behind them could agree on a common network protocol.
And the more compositor implementations, the merrier, a bit like the x11 window managers.
I am coding mine for linux and AMD GPUs, as a hobby, in RISC-V assembly running on x86_64 via an interpreter (thanks to wayland being an IPC interface)... well until very recently, it has been more some kind of research and development of a "method" to code modular assembly projects with a minimal SDK, in other words to decide on various technical compromises requiring coding _real life_ software in order to hit the right sweet spot.
I don't think Wayland is fully ready, at least not with NVIDIA GPUs with limited GPU memory. I have a 7,000 word blog post and demo videos coming out this Tuesday with the details but I think I uncovered a driver bug having switched to native Linux a week ago with a low GPU memory card (750 Ti). Basically on Wayland, apps that request GPU memory will typically crash if there's no more GPU memory to allocate where as…