137 karma · joined January 6, 2023
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...
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.
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.
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.
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?
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.
- 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.
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.
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.
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.
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.