HNHacker News
TopNewBestAskShowJobs

Crysstalis

139 karma · joined July 5, 2022

submissionscomments
Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
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 because you have to manually type in the coordinates and screen sizes which is at odds with how you would configure a graphical screen. If you want to set them based on some logic or calculations, you are better off reaching for a python script or something that is actually pleasant to write code in, and then use that to invoke the real API, not command line tools.
Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
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 with their own theme and override the system theme.

GNOME's regards towards theming is precisely because of things like Qt themes being broken all the time.

Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
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.
Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
That is how all other remoting solutions work. X11 forwarding just happens to be the worst one.
Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
>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 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.

Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
>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.

Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
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 to configure their laptop when they connect it to a projector.

Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
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 were very hacky and the code was a mess. IIRC the only desktop that actually did it was Unity, and that was discontinued. So you can see some of the troubles with that approach.
Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
>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 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.

Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
>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 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.

Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
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 default state of things in open source.
Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
>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 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.

Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
X11 forwarding is not even the best option for remote rendering on X11. You will get better results with VNC or NX/Xpra.
Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
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 direction that you suggest.

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.

Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
>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-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.

Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
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.
Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
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 protocols.
Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
>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 Wayland. So there is no reason it should be causing such a performance hit.

Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
Somebody could design that but it is not clear why you would. You do not need a separate process for that.
Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
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/

Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
>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.

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.

Crysstalis··on Ask HN: When do you think Wayland will be broadly supported?
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.
Crysstalis··on Everyone seems to forget why GNOME and GNOME 3 and Unity happened
>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.

>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.

Crysstalis··on Gnome Turns 25
>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 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.

Crysstalis··on Everyone seems to forget why GNOME and GNOME 3 and Unity happened
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 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.

Crysstalis··on Everyone seems to forget why GNOME and GNOME 3 and Unity happened
>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 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.

Crysstalis··on Everyone seems to forget why GNOME and GNOME 3 and Unity happened
>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 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.

Crysstalis··on Everyone seems to forget why GNOME and GNOME 3 and Unity happened
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.
Crysstalis··on Gnome Turns 25
>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 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.

Crysstalis··on Gnome Turns 25
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/-/issues/5026

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.

← PreviousPage 2 of 5Next →