139 karma · joined July 5, 2022
GNOME's regards towards theming is precisely because of things like Qt themes being broken all the time.
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 interfaces by themselves are actually very poor for automation and integration, as they force you to do lots of unnecessary formatting and parsing in and out of text strings at every step.
For graphical tasks such as this, the command line is indeed obsolete. The main usage for remaining with the command line in modern times is for manual administration of a remote server, but that is not relevant here as the whole problem space is about administering the local machine as a GUI.
That did already happen, Weston had a built in screenshot tool. Pipewire was adopted because it was an improvement on the Weston design.
And somehow, I doubt that even the most fervent of fiddlers really enjoy typing obscure command line incantations just to configure their laptop when they connect it to a projector.
This is exactly what Wayland has done though. Few have a reason to run command line tools to change the screen configuration, real world usage is to use a GUI as is common on every other graphical OS.
>You can pass resolution, refresh rate, position and orientation via command line in a simple and understandable way.
A major problem here is because of the way the API works, technically any X11 client can do that at any time. The tool may seem trivial but the way it is implemented has great potential for misuse. It does not even have to be malware for this to cause problems, for example a typo in a random script could seriously screw up your screen. Or another common problem in X11 is with applications setting the resolution to something weird, crashing and then leaving the screen in a weird state.
>This completely confirms second system syndrome. It's only as complicated and non-trivial as you want it to be. I can only imagine what kind of convoluted security nonsense you think of when you say "the right way". Ask the display server for a list of screens and supported resolutions, and then tell it what you want to do with those.
If this was second system syndrome, then it would be in the kernel, not in X or Wayland. Because the kernel is where all the new KMS features happened. Again, the display server is not actually driving this feature. They are relaying information to and from KMS, which is the actual API that configures the screen.
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 everybody always just used X.org despite its shortcomings. And by the way, freedesktop.org has for the most part merged with X.org now. It is the same group of people doing the same work.
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 holy hell my OSS desktop is not a proprietary smartphone OS loaded with random closed-source apps from god knows who that tries to steal my data for profit
I think it is not reasonable for you to ask them to never plan for a day when that could happen, if that is what you are suggesting anyway.
>You'd assume there's an equivalent tool for Wayland
Not if you were aware of the current issues with Xrandr and why it is a poor target.
>But mumble mumble security, you cannot do that, so we got the same f#+ing situation as with screen recording again, every WM/compositor comes up with their own solution to something absolutely trivial. GNOME/Mutter have a dbus-API, wlroots-based ones have "wlrandr" via some protocol extension, KWIN I didn't even bother checking. But it's only 15 years since the project started right, why should something trivial as this have been settled upon yet?
It is absolutely not trivial, and there are security/usability issues with it. To do this "the right way" would be more or less duplicating the entire KMS API into every implementation. Even XRandr is still missing features compared to that, so it is not an adequate solution either.
There is a remote possibility that some person comes along and builds a server and library that will work for everybody. But such things would probably be very large, much larger than systemd. Actually, the closest thing to what you describe is probably a web browser and HTML5, but building a desktop on that seems to be not popular aside from Chrome OS.
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-portal/pull/711
>no forethought to screen capture
The plan for a while has been to put screen capture in Pipewire, this is already working for apps that support it.
In any case, X11 also does not have any forethought in relation to hotkeys or screen capture. Technically it has no API for either of those, it has APIs that allow all applications to intercept all keys, and to allow all applications to read the contents of any window. Those APIs can be used to do hotkeys and screen capture in a rudimentary and somewhat broken way but they are not ideal. Just copying those (or an API that looks like those) into Wayland would be an unwise idea.
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 Wayland. So there is no reason it should be causing such a performance hit.
Regarding the issue of "choice", please read this page: http://www.islinuxaboutchoice.com/
No, not really. Everything that Wayland does is stuff that X11 compositors were already doing. With those the compositor is already taking on all processing of input, and the X11 server is only creating an additional unnecessary step by passing all the input through. Thus why that extra step was removed in Wayland.
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.
>Yes, it was terrible, people hated the change and that it was hard to make it work like the older versions, it's still famous for being horrible and unusable and MS basically rolled it back in the face of overwhelming criticism.
I think this is still a poor example to illustrate your point. They rolled back some aspects, other aspects were changed in Windows 10 and now again in Windows 11.
>I never claimed that only the gnome people have done this
Yes, my point was that they all do it. It makes no sense to fixate on GNOME doing this.
>Yep, and you could always switch back and forth, easily. Gnome 3 was scorched earth.
I am not sure what this is supposed to mean. You could always switch easily, even now there are many distros that offer GNOME as only an option, or do not really have GNOME as a supported option at all. Maybe you were using a distro that only supported one option, but it was always within their authority to do that just like they could decide to only offer KDE Plasma as an option. So this complaint still makes no sense to me.
>Yet here I am, and here most people on Windows are, and on OS X. MacOS X from 2001 is still recognisable today. Move the start button on Windows 11 to the left and you've basically got an evolved Win 95/NT 4.
Again that is describing one specific area, other things have been completely redone or rewritten. And I have spoken to some other people who were very bothered by that change and didn't like it.
>Evolutionary changes and improvements are great. People choosing to work differently is great. Designers exploring different ways of working, great. Wading in and hamfistedly breaking everything about how people work, then telling them they're wrong for wanting to keep working that way, is virtually never well received.
Just to clarify, it is very possible for a user to be wrong about something. If someone is telling you they are never wrong, that will virtually never be well received either. It is very hard for me to interpret this in a way other than that you're describing changes that don't bother you as "evolutionary" but ones that do bother you as "hamfisted". Try to be a little bit more objective about this, perhaps if you feel like it, go through a list of many changes across these and compare them. You might be surprised as to what you find.
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 every possible feature that ever gets suggested, or even to maintain the current feature set indefinitely without removing something at some point.
>The particularly awful disease the Gnome project has is the "rewrite everything" disease. No software project can retain features if they do large rewrites from scratch every major release.
You are confusing refactoring with rewriting. Very few parts of it have been rewritten from scratch. Refactoring things isn't a "disease". Refactors are actually necessary to keep the project in working order and to pay off technical debt so you can actually have a chance to implement new features while retaining older ones.
>The end result is that features the developers personally don't care for don't get implemented in the new release.
This is the same as any project. If there are no developers to maintain the feature then it stagnates and eventually gets cut. It makes no sense to be pissed off at this one particular project about this, every project is bound to do it eventually. If your company ever went through layoffs then you can probably name some times you have had to do this at work.
Anyway, the way to fix that would be to donate more to the foundation or to individual developers. In most open source projects, the non-profit foundation is not usually the primary source of engineers because they make a tiny amount of money compared to what the big enterprises do. But it is not very likely you will ever escape that tug-of-war, because developing an entire OS is very expensive.
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 changed their UI, some have done it several times. Remember the initial switch to Windows 8, or MacOS X, or from GNOME 1 to GNOME 2? And even before that, how Linux distributions had frequently been switching between window managers or from GNOME to KDE and vice versa? It makes no sense to me to take issue with this one specific case. For a project that is trying to keep attracting new users, it is unreasonable to expect them to never change anything or never refactor the UI.
The real WTF is using something like XFCE and expecting nothing to change for 20 or more years, that is totally out of the ordinary with any comparable retail tech product.
I really doubt that. MATE exists as a continuation of GNOME 2 and it is just not very popular. The users who care about such things seem to be a very small minority.
>X11 is the GUI server that most desktop Linux users use as of 2022!
This is not the issue. The issue is the number of developers who are interested in working on the X11 support in GTK is shrinking. If there are no developers to actually work on it then it simply cannot be done, what the users use is not relevant anymore.
>Have an ounce of respect for your users, and at least ask if that's what people want / are comfortable dropping.
>if a good chunk of the Linux userbase uses your software, then it's good to at least ask if people are OK with the direction being taken.
There is no point to asking this. If you ask most users whether they want you to continue doing free work for them indefinitely, of course they will probably say yes. There is a contingent who never wants anything to become deprecated just out of principle.
I do not understand this. Firefox and those other apps are not beholden to GNOME, they can implement any file chooser they have an interest in implementing. If they have chosen the same one as GNOME then it is likely because they prioritize implementing with GNOME over other things, so you will have to accept that those applications are not as interested in bothering to be independent of desktop environment. Some applications will always be like this, for example Thunar is designed for XFCE and it does not fit in so well with Plasma.
>I think the devs (or the HIG architects) have blundered in prioritising search over find and I want to see it corrected.
It is not useful to say this without having some kind of larger justification for it. Just repeating this is an anecdote, it is not going to change minds. If you want another anecdote, I have never liked find, I found it worse than search in every way. If I keep pushing from this angle and telling you that I want to see your opinion corrected, would that convince you? I doubt it would.
It is not possible in open source to force everyone to use one toolkit, in my opinion you are wasting your time by wishing for that. There are dozens of toolkits to choose from and the number seems to be growing. The fragmentation has only gotten stronger over the last 25 years, if Qt was the clear winner the proliferation would have stopped long ago. Now there is pretty much no chance that you will be able to hack every toolkit to get all of them to look and work consistently. In particular, the way an app works is decided by the HIG it follows, not the theme. This is reflected in the entire design of the app, to change it requires redesigning the whole app. It cannot be changed just by setting some environment variables.