HNHacker News
TopNewBestAskShowJobs

QUrprUd1nCeicw

137 karma · joined January 6, 2023

submissionscomments
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
Freedesktop standards can't include everything, it only makes sense to standardize "lowest common denominator" features that you know every desktop won't have a problem implementing. And since this is all open source and everyone can do whatever they want, participation in freedesktop is voluntary anyway. You can do the best possible job you can writing a standard and some desktop can still reject it for any reason they want.
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
That's the way it is with any optional X11 or Wayland extension. Either you implement the extension yourself, or you use a library to implement it for you. Typically the code to do this is put in a toolkit, but you decided to write your own toolkit so you get to deal with the annoyance. Nothing's changed in this regard. Actually, most optional things in Linux are like this and it's been this way since shared libraries were implemented. If you find the idea of this so off-putting, maybe you should be using a pre-made toolkit instead of writing your own?
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
No, this particular "reputation" you're referring to is a lie and a fabrication based on nothing, in order to push a narrative. I mean you literally just walked it back right now, in literally the same sentence. The people choosing GTK are choosing to do that, they're not being bullied by anybody. I don't think anyone is developing anything for the express purpose of trying to "win" a stack overflow survey.
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
Yeah that's fine if you prefer the default KDE workflow. If you prefer a different workflow, you have to either spend a lot of time configuring it, or use something else.
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
No it really doesn't. I've seen tons of Qt themes that break apps. Their theming system is similar to the design of GTK's, so it has most of the same problems. This isn't a technical problem, it's entirely a social problem: users want these themes but the same users are also under the false impression that you can ever have this type of theme that won't also break apps. When that isn't technically possible and it never will be.
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
Cinnamon is also way behind on the tech. They're still stuck on GTK3 and X11. The resources going to KDE to reduce jankiness is only going to KDE. It isn't going to GNOME. I can't see why you think that would have any effect on anything else.

Did you bother to read that whole thread? The developer gives a long explanation with the reasons: https://discourse.gnome.org/t/icon-view-sizes-in-nautilus-43...

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
The change may be in areas you don't see. Refactoring is something visible only to developers but it has to be done continuously to be able to pay down tech debt. FYI dbus is also used by KDE, XFCE and MATE. Please avoid making more criticisms like this. Volunteers really aren't going to listen to you if you can't even get the basic facts right.
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
All of those alternatives are notorious for having a release schedule slower than molasses, or for having outdated tech, or for having a lot of bugs. That's the price you pay, nothing is for free in this world. You mentioned they had more functionality in some ways but you neglected to mention why that is. Also it's funny that you think GNOME has any spare time or financial resources. Every GNOME developer I've ever talked to has been overloaded with low-paying or non-paying work, same as any open source developer.

The rest of your comment is dangerously close to toxic entitlement. You don't get to say you have no patience. Or rather, you can say it, but it's completely meaningless for you to do so unless you were trying to antagonize some volunteers. Avoid that line of thinking. These are all volunteers who can spend their time as they want.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
It's not healthy to find yourself getting angry at decisions made by random open source projects. I really doubt anyone working on that has as strong opinions as you on what the file picker looks like, or they would have written one themselves by now. None of these projects owe anybody anything anyway, that's kind of the point of open sourcing things for free without any warranty.
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
Did you actually bother reading any of the arguments on that page? They don't want distros to use themes because themes always break apps. This is unavoidable. There's no practical way to make those kind of themes in a way that won't break apps eventually. Tinkering is completely different from a distro shipping broken apps by default, it's understood that's your responsibility when you break everything yourself by tinkering after-the-fact. If you wonder why they might also make it harder for this kind of tinkering, it's because tinkerers also don't like to use something that will just break everything else!
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
That user isn't mythical. I'm a developer and I like GNOME's simplifications. I prefer to spend less time messing about with my window manager and more time actually, you know, developing. If you ask me, the idea that technical people need to spend months hacking around their desktop and fighting with thousands of mutually incompatible config settings just to get it to work is a harmful stereotype perpetuated by the more toxic aspects of the Linux community.
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
>Commercial developers who don't personally use GNOME at home and only only work on it because it's their job.

You're acting like this is a bad thing but that's how open source is supposed to work. Every contributor works on their area of interest. For companies, they work on what helps their customers. There's a practical limit to how many users any contributor can support because developer time is a finite resource. With many contributors it's supposed to average out over time into something more general use. However the Linux desktop has historically been very bad at attracting a lot of corporate contributors. That's not specific to GNOME and it has nothing to do with corporate interests, plenty of other desktops are even more minimalistic and hostile to design changes.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
>This is all assuming you want to use DBus. Why? Wayland is already the thing that you speak to talk to the display server. Why use another protocol for basic functions like this?

You have this completely backwards. Dbus was already standard on nearly every X11 desktop and was spoken by a lot of X11 window managers, before Wayland even existed. It was adopted during the X11 days because X11 is a poor IPC for anything outside of window management. It's notably bad at syncing settings where you commonly have an external process storing a settings database that sends notifications to interested applications. X11 is a poor fit for that, but dbus is great at handling that case with its signaling mechanism. Mouse cursor size being a good example of that type of setting.

>If DBus is so great, why do we even need the Wayland protocols in the first place?

Because they're two different protocols with different goals. Dbus is a general-purpose IPC that can be used for a lot of desktop tasks, like syncing settings. It's designed for many-to-many communication between every program on the system. Wayland is designed mainly for high performance between only one application (the window server) and its clients.

>Dbus is not great.

Dbus is the worst option except for all the others. I've seen a lot of dbus hate over the years but still no one has ever been able to propose a replacement. No, putting everything into Wayland protocols is not a suitable replacement.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
>The Gnome people seem to seriously just go around removing options because deleting working code used by actual humans makes them feel more powerful

They do it because open source projects don't have infinite resources to maintain infinite options forever. You can complain about it all you want, but 25 years of history shows that just because something was being used by humans doesn't mean that volunteers are going to magically show up to maintain that option for eternity. I'm sure if you've been working in this field for a while then you've deleted some unfortunate code in your day job and had to convince users to do things a better way. So why single out GNOME for this?

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
>It doesn't violate the letter of the GPL, but it sure as hell violates the spirit.

No it doesn't. The spirit of the GPL is essentially "do whatever you want with this as long as you keep distributing the source code." That's it. It says nothing about paid products or development style or keeping a certain style or direction or anything like that. The GNOME developers decided to change direction themselves, as the GPL says anyone can. It would no sense for them to give up their trademark to MATE when that was just a random offshoot that no one had any idea of whether it was serious or how long it would last. It's not even that active now, can you honestly say they would have benefited any more from having the GNOME name?

Like, come on my guy, you're flogging a horse that died more than a decade ago. You can continue this substance-free criticism of open source projects for as long as you want, just be aware that you get out what you put in.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
Then maybe you should use one of those projects instead of GNOME? What's the problem here?
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
That "reputation" is complete nonsense. Outside of HN (and a few other places with low-quality moderation) I don't see anyone trying to push that "reputation" as a narrative. GNOME has no other option but to dismiss and ignore those claims. I mean it's literally "you're bullying me because you don't do what I'm demanding you to do right when I want you to do it."
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
Applications shouldn't use libwayland directly unless you're planning to implement your own toolkit and event loop and threading abstraction yourself. It's certainly a take to do things in the most complex way and then complain that you have to implement a lot of complexity. Off the top of my head, here are things that won't work that way unless you implement them yourself:

- Networking. The socket(s) will block your program loop.

- Audio. Has to be done on a separate thread with strict timing.

- Background loading. Get ready for your program to hang when loading a large file.

- Talking to any system services. Every common desktop uses dbus now. Really. Using sway on an embedded system without dbus is a niche.

- Power saving modes. Without an event loop you always have to use sleep to poll yourself manually, and that's wasteful.

- Simulations, physics, or anything else that requires a constant tick rate. These are dependent on running the rendering in another thread.

- Accurate timers. Any issues with any of the above will block a timer from firing.

There are probably a lot more too. What seems "lightweight" first can turn out actually not be lightweight at all.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
>Basically GNOME is living in and pushing a world where there's only GNOME.

No, that's false. I can't see why you'd even think that. GNOME wouldn't be using Wayland at all if that were true. GNOME uses standards where they make sense, this one optional non-standard part of Wayland just happens to not make any sense for GNOME. They don't have any issue with the rest of Wayland.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
That's not a good comparison. To get a full picture, you have to compare the X server, all the Xorg drivers, the X client libraries, the X utilities, all the different X window managers and compositors, all the code from alternate X server implementations, etc. X11 desktops are all using dbus too so that one counts for both. All together added up it's significantly more code than Wayland, and that's even considering that the major Wayland compositors try to share as much as possible between the X and Wayland implementations. That is, Mutter and KWin didn't use wlroots. Wayland and X11 are just pluggable backends for them. Go and look there yourself if you want to make your own direct comparison. The Wayland backends are pretty small and they talk to the kernel directly, whereas the X backends have to go through all of that extra code just to talk a complicated protocol to the X server to accomplish the same task.

This is different situation for older non-compositing window managers that still use the old X11 drawing primitives. Compositors do all their drawing themselves using direct rendering to the GPU so are able to just swap out the backend without much trouble. That shift was happening in X11 in the years prior to Wayland and it's one of the reasons Wayland is even able to work.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
>you either have to add GTK as a dependency to get the "correct looking" titlebars or spend useful development time writing shitty, non-native looking window decorations just for GNOME users

That's a false dilemma. You don't have to do either of those. The alternate solution is mentioned in that issue: use libdecor. I'll also note, if you refuse to use any of the system's UI and you insist on implement everything yourself directly on libwayland then that's an entirely self-inflicted problem that you created. Libwayland is fairly low-level, it isn't a game development API. Besides window decorations, you'll have lots of other deficiencies and things you have to spend development time on. That's what you volunteered for, GNOME can't help you with that.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
There's nothing wrong with that statement though. It's literally true. GNOME, Ubuntu and XFCE all have different APIs that conflict with each other. The situation is a bit better now that Ubuntu dropped Unity but that was a decision they had to make by themselves, GNOME couldn't do anything about it. What else do you expect them to do? Any time Ubuntu or XFCE decides to keep some API that breaks GNOME, or worse, decides to implement some new API, GNOME has to drop their own plans and maintain it forever? That doesn't make any sense no matter which way you look at it. You're shooting at some random GNOME dev for playing the role of messenger instead of addressing the root cause.

I also see nothing wrong with the second thread. GNOME is under no obligation to implement features they don't want to implement. You're posting that to push a narrative while ignoring the other hundreds (thousands?) of bugs that get fixed without any fanfare and without the HN crowd throwing a multi-year long tantrum. It's quite frankly embarrassing to see these brought up continually as an attempt to criticize GNOME. You can do better than this for the Linux community.

← PreviousPage 4 of 4