Crysstalis

8 ms·

31.
by Crysstalis 4y ago
But that is where you hit impedance mismatch. Some things that are easy to represent in a GUI (because they are graphical tasks) cannot be easily represented in a command line tool. XRandr is probably the worst example of a scriptable tool
32.
by Crysstalis 4y ago
That unfortunately is a Qt bug, not specifically a Wayland bug. An issue should be filed there if it is not already. But, it is not likely you will be able to correct it for every app, because Qt apps can technically do whatever they want w
33.
by Crysstalis 4y ago
No, you can just install it if you need it. It is just another package, there is no special reason it needs to be default.
34.
by Crysstalis 4y ago
That is how all other remoting solutions work. X11 forwarding just happens to be the worst one.
35.
by Crysstalis 4y ago
>The ability to automate and integrate with a huge ecosystem of compatible tools What you are thinking of is an API, not a command line interface. That still exists, and it can be used to build a command line interface. Command line inte
36.
by Crysstalis 4y ago
>how do we design both a secure system and one that allows screenshots and screen sharing? That did already happen, Weston had a built in screenshot tool. Pipewire was adopted because it was an improvement on the Weston design.
37.
by Crysstalis 4y ago
But you can still fiddle. Unless I missed something, the only complaint here is that the method of fiddling has changed. And somehow, I doubt that even the most fervent of fiddlers really enjoy typing obscure command line incantations just
38.
by Crysstalis 4y ago
I remember at the time the Compiz developers were trying to get everyone else to either base their compositor on Compiz, or build in support for Compiz plugins. That might have been feasible if there was a working design, but Compiz plugins
39.
by Crysstalis 4y ago
>Then plan for it, architecturally, so that you can add or enable these features later on, or when you need it. Start with something sensible, appropriate for real-world usage. This is exactly what Wayland has done though. Few have a rea
40.
by Crysstalis 4y ago
>Wayland is not really simpler than X11 unfortunately. I would say it is. All the things you said are also true of X11 and are worse there, which is another reason why it has been so impractical to develop additional X11 servers, and why
41.
by Crysstalis 4y ago
So then you have to come up with a plugin system which everyone wants, which is probably not even possible because the definition of "plugin" is so vague that it could mean anything. If you ask me, fragmentation is just the defaul
42.
by Crysstalis 4y ago
>And second system syndrome too probably In my opinion, Wayland has avoided this by deliberately being simpler than X11. > I'm using $DISTRO because I trust them enough to not package spyware/malware in their repos >but h
43.
by Crysstalis 4y ago
X11 forwarding is not even the best option for remote rendering on X11. You will get better results with VNC or NX/Xpra.
44.
by Crysstalis 4y ago
Please see one of my other replies here. When implementing an X11 compositor those parts were already done separately anyway, and this is actually the entire point of X11 compositing. So the trend with X11 was already going away from the di
45.
by Crysstalis 4y ago
>no forethought given to apps that need global keybinds Please see this pull request for a description of some of the current challenges with getting global shortcuts to work: https://github.com/flatpak/xdg-desktop-p
46.
by Crysstalis 4y ago
Doing so requires writing a server and library that everyone can agree on, which probably will not happen and is probably one of the main reasons they did not do it in the first place.
47.
by Crysstalis 4y ago
You still had the same problems in X. It was a bad idea to try to get protocol code merged into X unless you could get everyone to agree on it. Because ultimately, in either case it is still the same set of people who will be using any new
48.
by Crysstalis 4y ago
>I get 25-50% more FPS in games using X than Wayland. This is probably just a bug. If you are using kwin compositing on X11, and not using the option that disables it for games, then it will be doing more or less the same thing as Waylan
49.
by Crysstalis 4y ago
Somebody could design that but it is not clear why you would. You do not need a separate process for that.
50.
by Crysstalis 4y ago
It is as modular as any compositor wants to make it, for example Weston has a plugin system. Regarding the issue of "choice", please read this page: http://www.islinuxaboutchoice.com/
51.
by Crysstalis 4y ago
>The greatest problem with the Wayland protocol is how much work a compositor has to do. Requiring every window manager to also have to take on tasks like processing keyboard and mouse input is a massive tradeoff for what Wayland offers.
52.
by Crysstalis 4y ago
Qt and Electron both support it, so those applications just need to enable it. It is hard to understand what else fits your definition of broad support, because you have only listed two applications.
53.
by Crysstalis 4y ago
>They really aren't. Actually they are, I cannot name a single system that has not changed in some significant ways since the 90s, unless development has slowed to the point where it basically stopped and became a time capsule. >
54.
by Crysstalis 4y ago
>I don't have time to spend hours arguing in favour of retaining a feature inside Gnome. Then perhaps you can see how developers of a desktop also do not have time to listen to every person arguing for every feature, or to maintain
55.
by Crysstalis 4y ago
That still does not give you any more control. Anyone can still change the project or fork it or do whatever, just they do not because only the engineers working on it are the ones who do get anything done. Anyway, the way to fix that would
56.
by Crysstalis 4y ago
>Does that explain it OK? No. The things you are saying are completely normal and expected, and I cannot see why you would be upset by that if you had been updating a Linux system (or any OS) for the years prior to that. Every OS has cha
57.
by Crysstalis 4y ago
>GNOME 3 would absolutely have not been pushed as the future of GNOME so unilaterally if the lead devs showed any restraint or signs of listening to their users, given how much initial outcry there was I really doubt that. MATE exists as
58.
by Crysstalis 4y ago
There is no "pay for a controlling stake", they either send engineers to work on it or they don't. GNOME is not a corporation, you cannot buy stock in it.
59.
by Crysstalis 4y ago
>1) It's not just Gnome that's affected, it's also the gtk3 FileChooserDialog, which is used by many applications (e.g. Firefox), independent of desktop environment. I do not understand this. Firefox and those other apps a
60.
by Crysstalis 4y ago
The short answer is because any flag will break other things. There is another suggestion to not require any flag, but it probably will not be implemented because of this: https://gitlab.gnome.org/GNOME/gtk/-/

More ›