HNHacker News
TopNewBestAskShowJobs

QUrprUd1nCeicw

137 karma · joined January 6, 2023

submissionscomments
QUrprUd1nCeicw··on X servers no longer allow byte-swapped clients
What? How did that marginalize anything? Solaris and BSD had their own init systems long before Linux had systemd, they didn't use sysvinit.
QUrprUd1nCeicw··on X servers no longer allow byte-swapped clients
Except that web interfaces will probably always be a better way to remotely access those devices.
QUrprUd1nCeicw··on Mastodon has gone from 2.5M active users in early December to 1.8M last week
>which reinforces certain accusations about the left's priorities

Which accusations? Donald Trump's Truth Social is a Mastodon instance.

>and Twitter's past inaction on the matter

Reports say as of this week, Twitter has fired even more of the moderation teams and the trust and safety teams.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
My original point was your criticism is lacking in substance and it needs to improve, and also your anger is misguided and unhealthy. I get that you're passionate about open source so that's why I'm explaining it. GNOME is just an open source project given away for free by community volunteers, it's not a business. They can't see you're upset and just charge you a hundred bucks to send customer service to your house to fix whatever missing thing you have on your computer. The anger is just going to go nowhere and rot, it's your responsibility to channel your energy in a productive direction, like actually being respectful and convincing people (with solid facts about design and tech issues) that your way is the right way.
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
>You said "changing the project from the inside", which a fork isn't.

Yeah, it is. The inside of the project being the code. You just fork it and change whatever you want. What else do you think that means in the context of software?

>Gnome is a business, same as Wikipedia

No, GNOME and Wikipedia are both non-profits. They're not businesses. "Business" usually means a for-profit company. In both GNOME and Wikipedia, the money is mostly all going to administration costs and costs to run the servers. Currently no GNOME developers are paid by the non-profit, and Wikipedia editors aren't paid either. Ask any of them and they'll verify this. I think you're confused as to how most non-profits actually operate.

I haven't said anyone gets a pass on criticism, I'm not sure why you're pushing that point. I don't think you should throw bad, low-effort angry criticism at businesses either. But open source projects aren't businesses, so I can't answer your question because it doesn't make any sense. Please ask a different question or rephrase it.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
>There are a bunch of barriers, you don't have to go far to see people asking if pull requests would be welcomed for a particular feature.

That isn't a barrier and you don't need to do that. You just implement the feature in your own fork. I can tell from this you're not a developer because this is a common confusion. When you ask for a pull request you're not trying to get through a social barrier. You're actually asking someone else to do you a huge favor by taking time out of their day to review your code for free. And then if they merge it you're also asking them to maintain it for free and fix future bugs in it for free. Normally you would have to pay to get other developers to do that.

>but it is a business

No, this is false and you're getting confused again. Some businesses can contribute by volunteering their employees' time, but that's different from the project itself being a business. The project itself (as in the collection of all the contributors) isn't deciding what those people are paid or what they work on. The project itself doesn't have the customers or answer to them, the business does and that's a separate entity both legally and functionally. Do you see how this is fundamentally different from a business?

>I don't think it gets a pass just for being open source, any more than the linux kernel or Wikipedia does.

A pass on what, exactly? You're coming back to this combative language again, please stop.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
I don't see how these questions are related. Those are businesses. Volunteer open source projects aren't businesses. There's no barriers for anyone to join the project and start changing it from the inside. And they're specifically set up so you don't have to boycott them when disagreements happen, you just fork the project.
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
I think I've already explained multiple times what good criticism is. I'll repeat it with some other tips. Always present criticism in a helpful way. Be as respectful as possible every time. Only give feedback that you yourself would be willing to hear from someone else. Make sure the other person is comfortable with you before offering criticism. Never offer criticism unless you're also willing to offer to help. Acknowledge that sometimes your criticism could be wrong and apologize when it is. Accept that sometimes you have no useful criticism to give and in those cases, the best course of action is to stay quiet. Present new information each time instead of repeating old information. Use the "feedback sandwich" and always pair your criticisms with equal or higher amounts of praise. Avoid criticizing in areas that you're not qualified in. For code, that means don't talk about it unless you've personally studied that code in detail. Avoid personal attacks. Avoid trash talking. Avoid starting fights. Avoid continuing old fights. Avoid holding grudges. Avoid rumors and hearsay. Avoid "ranking" people against each other. Never look at anything in terms of "opposing sides." Avoid creating situations where one person wins and the other loses. Remember that everyone is on the same team and as a good community member, the ultimate goal of your criticism is to support others and create situations where everyone can win.

This is fairly generic advice and it all isn't even related to GNOME. This is a general guideline for any healthy community. You can read about all this in random books about community building. If you want to be part of open source you just have to be a good community member, there's literally nothing else to open source. That's why I say it's unacceptable to do those negative things. There just isn't any other way this works. These are communities of equals, you aren't the boss and no one else is your boss either, so it's on you to manage your own conduct.

I'm trying to be kind to you but you're making it difficult when you lead by saying nasty things about people I know, like they're acting shitty just because they declined to implement a feature that you were personally invested in and they weren't. And you keep insisting that they have to do this or they deserve it or something like that. Please just don't do that, it makes it extremely hard to engage with you when I have to keep going through this wall of "but don't you see this other person sucks" or that type of thing. You're automatically putting everyone else on defense when you do that and it messes up the whole conversation.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
>That negativity has been for the most part earned.

No, it hasn't. It's unacceptable for you to make personal attacks calling them "shitty people" because they closed a bug report. It's unacceptable for you to demand that open source developers spend their time addressing your concerns for free. Period. End of story. This isn't up for debate and you're acting like a troll by constantly coming back on this. So I'm asking as person, can you just stop this behavior, please. If you can't agree this is unacceptable, you'll always be a toxic participant in open source. I'm not even exaggerating here. Open source developers will never owe you anything, the entire point of it is it's all voluntary and any contributor can come and go at any time they please. Read this article if you want to know more about why this type of toxic entitlement is always harmful: https://mikemcquaid.com/entitlement-in-open-source/

>You may disagree on that criticism, but from where I'm sitting it was legitimate.

And I'm telling you it's not. You're sitting in a place with incorrect information.

>Things like "I would be happy if they stop opposing server side decorations in Wayland" is entirely appropriate

First of all, that's not what you said originally. You're walking it back again. I wish you would just be honest and apologize and say you were out of line before. Second of all, they're not doing that. Your statement is incorrect and misleading. GNOME isn't opposed to anyone else implementing server side decorations in Wayland. There's just no point to them implementing it in GNOME.

>That's about the most passive and polite way to criticize Gnome I can imagine

Well you need to imagine harder because that wasn't passive. You're framing it like GNOME is actively standing in the way blocking someone from implementing server side decorations, when they've never done that. You can put server side decorations in your own Wayland implementation, or use another one like KDE that already has it. GNOME can't "oppose" anyone from doing that.

>I do that mostly because I don't want to call out individual contributors by name

You already did call them out by name. Again, if you have a disagreement with an individual contributor, you should talk it out with them instead of trash talking them behind their back on social media. Trash talking makes your behavior frustrating to deal with because nobody can trust you not to start fights.

>Gnome doesn't want to implement XDG-decoration, which is fine, but don't pretend the opposition is going against the facts here.

There's no "opposition," this isn't a fight or a debate and it never was. Open source is a team sport and the other team you play against is the computer. It's not about people vs other people. Either you're helping out the team working on the code or you're not. You're still framing this in needlessly confrontational and combative terms, this needs to stop.

>When we debate "should gnome implement the XDG-decoration spec" we're actually debating a lot of more ephemeral subjective stuff

No, there's no debate to be had here. If you were serious about discussing these issues you'd take it up with the GNOME design team. In a sense their decisions are subjective but they don't just make them at random. They're trying to make a consistent system within a particular framework targeted at a particular set of users. And the same things about development apply to them too. Nobody on the design team gets to "win" every debate. Some ideas are just bad and they lose and get thrown out. All the things you're saying have been discussed to death already. Do you think the design team hasn't heard this already in the years previously when these were brought up before? They have, you're not making any new arguments that would ever be convincing. You're just saying "I wish they would implement this" and that's like, ok? All the GNOME designers have about 1000 features they want to implement too, but time is limited so realistically they can only pick a few and they have to throw out the rest.

QUrprUd1nCeicw··on X servers no longer allow byte-swapped clients
I can't understand the situation here. Why wouldn't a more recent OS release have a VNC server available? And why is a web server being used to run firefox? Shouldn't that be run on the client? Why are you even installing a GUI on a Unix server? It seems to me like something is very backwards about your setup.
QUrprUd1nCeicw··on X servers no longer allow byte-swapped clients
If your IT department at work refuses to give you a modern solution I think that's their problem, not yours. They should just know, X11 forwarding was already obsolete decades ago. They're just signing up for trouble and misery with that.

I doubt that X11 is going to disappear for good. It will still always be around for running the odd old X client or for historical curiosity. Just like how you can still emulate the original Macintosh (released the same year as the original version of X!).

QUrprUd1nCeicw··on X servers no longer allow byte-swapped clients
I mean if you have a high bandwidth connection and you want to only transfer raw uncompressed software-rendered images then sure, go nuts. For me that lags horribly and it's pretty much broken if you try to remote a fullscreen window above 1080p. It's not exactly "network transparent" if it only works in a very contrived network situation. What do you think a remoting protocol is supposed to do if not compensating for bandwidth and latency issues? These are really basic things (bandwidth negotiation, latency compensation) but they were just never added to X11. And it's not like people didn't try to add them either!

Edit: I want to say that nearly everything in X11 is like this. It seems to work ok at first glance but it breaks horribly when you get outside the design parameters of a mainframe in 1987. So basically, transferring software-rendered images over a high-bandwidth LAN connection and that's it.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
>Members of the Gnome project have a long history of being disrespectful to their users and to other open source projects.

No. You're confusing a normal disagreement with disrespect. There's nothing disrespectful about saying "no we're not going to implement this." I assume from this confusion that you don't work in this field. If you work as a developer you get used to saying things like that all the time. Most users don't understand code. Why would they? Users come at developers with all kinds of requests, some good and some bad, and it's the developers' job to make a decision to say yes or no.

>Honestly? I think we're past the point where Gnome is going to really cooperate

Cooperate with who? If you want them to cooperate with you, then you need to respect them. That way they'll owe you the respect you give them. That means putting aside all the past anger you might have and practicing forgiveness. Put aside any old opinions you had and start fresh. This isn't related to GNOME by the way, this is for any project that you may have a disagreement with. Just think how this would be if the situations were switched and somebody wanted something from you for free. The ball is completely in your court because they're not the ones going on social media making long posts about how you should write some code for them!

>It can be hard to dig yourself out of a reputational hole, but I do think it's largely a Gnome attitude problem. Or maybe just a Gnome communication problem.

Unfortunately in this case it's neither. I can name some times when GNOME screwed up communications but this one isn't that.

>I think better developers than me explained why, while technically correct, that stance is harmful to the open source community as a whole. (they do get some points for libdecor) I can't do a better job of explaining it than those developers, and if you don't see the problem there than I don't think we're going to be able to reach any sort of common ground.

There's no "stance" it's just a statement of facts. This is the way things are. Call it harmful or not, GNOME developers can't change it. I see the problem, what you're not seeing is that the problem isn't fixable in the way you think it is. You still seem to think this is a "stance" or "opinion" that some developer has and not an unchangeable fact of the code. Why? If you can't explain this well then maybe consider that you're not qualified to be commenting on it?

>and honestly I hope that libadwaita makes GTK more useful for non-gnome apps

This already happened, have a look at what ElementaryOS is doing.

>Where as you seem to need to find a reason to dismiss every single Gnome criticism there is, I don't think you've admitted to any Gnome flaws throughout all of this.

I can list a bunch but I don't want to. I don't bother discussing my own opinions about GNOME on HN any more because every time I do, people who hold opinions like yours use it as an excuse to turn it into a GNOME hate-fest flamewar and start harassing the developers, calling them shitty bad people who deserve to get their reputations trashed. That stuff is unacceptable. I'm serious here when I say this. In my opinion it's your attitude that's poisoning the well. And this is why I use a throwaway account to discuss this by the way. For whatever reason the moderators here think it's ok for this to be a place where trolls and conspiracy theorists run amok. I'm glad you have some good things to say about them but the toxic negativity really needs to end.

QUrprUd1nCeicw··on X servers no longer allow byte-swapped clients
That only ever worked for ancient OpenGL versions. There's basically no chance you can get modern OpenGL/Vulkan/Direct3D/Metal working like that.
QUrprUd1nCeicw··on X servers no longer allow byte-swapped clients
The common web browsers or web-based apps are all using hardware accelerated Skia. Almost nothing uses the core X11 APIs anymore.

I'm honestly confused when I hear people say they still use X forwarding and it has no slowdown. It's known to be one of the worst possible options for remoting, the core protocol doesn't even support image/video compression. RDP runs circles around it.

QUrprUd1nCeicw··on X servers no longer allow byte-swapped clients
>If it works fine, why not import it into the project?

Why? The shim is generic, it's for porting any Linux programs.

>And an important distinction here is that the drivers issue pertains to Weston

It would also affect the other Wayland implementations, which would need to adopt the same driver system. Those drivers would have to duplicate a lot of code from DRM and Mesa, it's just not worth it to put all that code into another library and then make Weston use it.

>But none of this need be debated if we just dropped the pretense that Wayland or the Wayland community cared about anything other than Linux.

Again, what is there to port to? Those other systems are behind in supporting the APIs needed for modern hardware. There's no alternative to DRM, GEM, KMS, etc.

>Wayland is simpler than X less because it's better designed and more because it redefined the problem. Network transparency? Not Wayland's problem. Portable across OS and driver environments? Not Wayland's problem. Input device management? Not Wayland's prob^W^W^W....

I think you know that X11 wasn't exactly good at any of that. I would think BSD users appreciate all of that because they all have different opinions on how all those things should be done.

QUrprUd1nCeicw··on X servers no longer allow byte-swapped clients
Well, this wasn't removed. It was just hidden behind a configuration setting.
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
That's not bias it's just bad writing. You could say there is bias if it was ever explained what the controversy was but it wasn't explained in that quote. If you think that's bad, you should see some of the really terrible incoherent anti-systemd and anti-GNOME rants I've seen over the years, that are completely riddled with insults and conspiracy theories. Please do your best to not be like that kind of ranting person.
QUrprUd1nCeicw··on X servers no longer allow byte-swapped clients
Are we reading the same thing? Those issues show that it materialized years ago:

>FreeBSD and NetBSD have epoll-shim which implements epoll through *BSD-specific kqueue

The shim works fine already, why fix what isn't broken?

And it's not that those other systems lack Linux-specific interfaces, it's that the ones missing those APIs lack any interfaces for these things at all! There's no way to be portable here, there's nothing to port to! If they decide to implement this eventually, why not copy the Linux API that's already open source and we already know it works, instead of reinventing the wheel? Alternately, Wayland implementations could add (limited) support for userspace drivers but why bother with this when we already know it's an inferior solution that should eventually be replaced with a kernel API anyway? And BSDs have already implemented parts of those APIs separately so we know they don't actually have a problem with them!

QUrprUd1nCeicw··on X servers no longer allow byte-swapped clients
There's no such thing as "network transparency" anymore. Newer desktop apps are now written to assume GPU rendering and that's local only, even on X11. If they implement software rendering at all, it's a separate code path provided as a slow fallback. If you were using X forwarding to run old clients, you can still use XWayland to forward them. It's the same idea as using XQuartz on Mac, you run rootless X11 on top of another window system. VNC should also work on every Wayland implementation I've seen.

Part of the reason Wayland is hard to port to other Unix systems is because most of them are really far behind in kernel APIs compared to Linux. Wayland doesn't really have userspace drivers like X11 did, the current implementations assume that the kernel is just going to handle all of this. The other kernels really need to be implementing evdev, DRM and KMS to get the full range of support for input and graphics hardware. Without those APIs, those other kernels are on their own trying to figure out how to get modern hardware to work and how they're going to plug random drivers into Wayland, when that model is obsolete as far as Linux is concerned.

QUrprUd1nCeicw··on X servers no longer allow byte-swapped clients
The problem with the X server code is most of the protocol code is very complex and it's hand rolled code predating C89. It (still!) does all the parsing and byte swaps manually. In a modern project you would have the compiler generate the parsers and the dispatch table based on an IDL but X is way too old to have done this. There are just two implementations in the code for everything. No one wants to touch it due to fear of breaking everything even worse. So instead they just slowly try to stop the bleeding by disabling things that cause the worst security issues. It's a bad situation overall, and the time has already passed for a full rewrite of the X server to be viable.

The SSH protocol is relatively simple by comparison, and most importantly, there actually are multiple independent modernized implementations of it.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
I was curious so I looked at the most recent stack overflow surveys that mention GTK. They actually say you're wrong.

https://survey.stackoverflow.co/2022/#section-most-popular-t...

https://survey.stackoverflow.co/2022/#section-most-loved-dre...

GTK has lower usage than Qt and Electron, but it's actually few percent higher on the "most loved" category than Qt and Electron. However all of them are below 50% loved. The percent GTK is above them is probably not enough to be important. And that's exactly what I'd expect: all these desktop toolkits have issues and are disliked. Electron and Qt are cross-platform so of course they would have higher usage than GTK, which has only ever really been popular on Linux. And none of it matters anyway. .NET wins it all by a large margin due to the popularity of Windows and the only other big GUI frameworks on there are Flutter and React Native. I'm honestly surprised GTK is even on the list at all, it wasn't there in previous years. I expected the list to be totally dominated by web frameworks and Python frameworks like it was before.

This is kind of along the lines of what I've been trying to communicate to you. Complaining about these minor issues and playing the blame game between open source projects is pointless. Microsoft, Facebook and Google are the big boys in town, that's not gonna change by GNOME fixing some random low-priority bug.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
>it is merely subjective.

Subjective as in, not based in any provable facts. Can you see why this isn't convincing? Is this really worth your time to go at it from that angle?

>This thread points at plenty of real examples of problems

No, you haven't mentioned any real problems. This discussion would have ended long ago if you did. I've been trying to point you in the direction where we talk about real problems and solutions but you're being very stubborn here. You keep trying to nit pick about perceived "rudeness" in comments from years ago that isn't even there. You're mistaking someone being short and to the point with being rude. Can you cut it out with this stuff already please? Why are you doing this? Please don't say something like "GNOME made me do it" because you know that's not true.

>I think the SDL developers in the lined thread did that

No, their suggestion wasn't convincing. Repeatedly making the same suggestion but louder each time isn't an improvement. You have to actually change the core of the suggestion and come up with new ideas, rather than continuously bringing up old ideas that it's already established they won't work.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
>Gnome as a project isn't entitled to that social capital, they have to earn it.

It's evident that every time they earn some, the haters invent new reasons to take it away by creating a new meme about how terrible GNOME is. The old meme about thumbnails in the file picker finally got fixed and you're just as angry at them as ever. Do you understand why they won't ever waste time trying to "earn" things from a group that's perpetually unhappy? I wish you would do yourself a favor and leave that group, it's not a group that's focused on actually solving any problems.

>The ball really is in gnome's court for this one. Some olive branched they could extend would be some kind of dconf setting to enable typeahead in the file picker

No it's not in their court. It's completely in yours. This is all open source, so you can just implement that if you want it, or use one of the many patches floating around. GNOME developers aren't under any obligation to pick up random patches off the internet that would increase their own support burden just because someone keeps asking, you can take those for yourself if you really want to deal with the mess. Like, come on. At what point will you stop blaming them and take responsibility for your own choices? At what point would you ever accept "no" for an answer? If the answer is "never" then you should be able to understand, it's you who's refusing to compromise.

>The SDL developers involved have some very concrete problems that they were trying to discuss civilly. The response from the maintainer? https://gitlab.gnome.org/GNOME/mutter/-/issues/217#note_3568...

That's a completely civil response based on facts. Core Wayland requires apps to support client decorations. The server side decorations are an optional extension. This hasn't changed in the four years since that response was posted. It makes no sense for you to be bringing this up again.

>It's a very rude response to a half dozen very maintainers of very prominent open source projects. SDL alone is a pretty big deal, if SDL is saying that your solution won't work for them then you listen, since basically all commercial application on linux use SDL.

No, nothing was rude about it. The only way I can interpret this attitude is "SDL is more important than you so they should get to strongarm everyone else into doing things the way they insist" and that's definitely a take. Is that what you meant? If that's true then you're saying SDL is the real bully, not GNOME.

>it means that everybody needs to create an extra special solution just for Gnome and if any other DE tried that SDL would rightly tell them to frig off.

It's not a special solution for GNOME, this is required by the core Wayland protocol.

>You don't think that interaction had any affect on Gnome's good will?

No, I think people who already had a negative opinion of GNOME and think GNOME is responsible for all evils in Linux would use that as fodder for their anger. If it wasn't that, they'd find something else to be mad and blame GNOME about. Like, my friend, you're doing it now.

>While we may not be forced to use it, they do throw their weight around and have significant effects on the open source community as a whole, so when they break stuff for people who don't even use gnome

No, every issue you've said so far only affects GNOME or GTK.

>But you're acting like we all owe the Gnome project our respect, and that's something I really don't get.

Yes, you do owe them some basic respect and dignity if you want them to cooperate with you. What's the part of this you don't get? Your disrespect is pointless and damaging to yourself because it's leading you to make nonsensical uninformed decisions and fail to understand other people's actual positions. If you have some disagreement with Matthias then you can talk it out with him like a human being and offer to help, instead of trash talking behind someone's back. These developers are real people you know? They're not code-writing robots who all obey a hive mind. I can guarantee you're not seeing the full picture here. If your reaction to this is "no, I will never talk to those evil GNOME developers until they fulfill my list of demands" then again, please consider that it's you who's being the unreasonable one.

>but stuff like that XDG-decoration thread and seeing how Matthias treated respected members of the open source community, completely disregarding their points and smugly refusing to engage in any technical discussion

There's no technical discussion to be had and no one was being smug or treating anyone badly. You're shooting the messenger. Again, this is required by the core Wayland protocol. You can be upset about this but the decision was already made years prior by other people outside of GNOME's control. GNOME can't change the core Wayland protocol because that would break existing apps. I'm telling you right now. The thing you're asking for is unreasonable. If you keep making this request, you'll only end up disappointed and you'll just piss more people off for no reason. Please approach this from a different angle and avoid the trap of saying "these developers are always right and must be listened to but these other developers are always wrong and must never be listened to" because that's what you're getting into and I think you're smart enough to see that's obviously a toxic way to think about anything.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
I think they would, if you met them where they were at.
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
>This is a shame. I'd be willing to help make it happen, by either writing code or helping fund someone else to

You might consider joining the IRC/Matrix channel and making an offer to one of the maintainers.

>Now for something like syncing the cursor size, that belongs in Wayland. Duh. The Wayland compositor handles displays, their scale factors, and the hardware cursor. It's just common sense.

No, unfortunately it doesn't and it isn't. You're describing something that isn't Wayland. I've seen upstream Wayland developers following the rule of "it should only be a Wayland protocol if it requires access to Wayland object ids" and idle-inhibit does follow that rule (you can inhibit on a window id). Anything to do with mouse settings doesn't follow that rule. There was a conscious decision to keep settings handling out of Wayland protocols because, among other reasons, Wayland is designed for a specific thing (windowing) and is bad at being a settings database. It doesn't really even have a way to identify hardware devices, those are all abstracted away under "outputs" and "seats" which don't actually need to correspond to any physical device.

>Aren't systemd user instances per user and not per session? How can you deal with DBus in that context?

You only have one session bus per user and it's the one used by systemd. I mean, you can start more buses but why would you need to when none of the services you want will be using that?

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
We could never have a fruitful conversation if all you were trying to do was trash talk some people. I won't engage you there. Once you abandon the idea that you need to tear other people down to make your point then you'll find our conversation will improve instantly.
QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
>Sure, I can't prove that their approach is doing immense damage

>that kind of behavior is shitty and makes them poor stewards of the project.

This is a perfect example of a useless, substance-free criticism. You can't prove what you're saying, you admit you don't really know what you're talking about, but you're happy to say they're shitty. It's like if you randomly walked into stores and said to the clerk "I can't prove it but you're a shitty person who's bad at your job" and then walked out. That would be like, ok? Do you think anyone is actually going to be motivated by that? Now just imagine you have a little website with your friends for your hobby and someone you don't know does this to you. They come along saying you're shit for not making everything exactly to their personal opinions. Can't you see how this is an awful way to participate in a supportive community?

Really now. Repeatedly making the same nonsensical requests and criticisms isn't going to help anyone. If you seriously expect them to improve their project then you should take the same advice: improve your own criticism. Make it so good and so respectful and so helpful they can't ignore your suggestions anymore. Avoid the personal attacks telling someone they're shitty and bad, instead think about how you can support that person and build them up to be better to accomplish great things.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
I'm not the author of this blog post. If I was, I would tell you.

>If you don't believe me believe the SDL dev, or the LXQT devs (formally LXDE, but they had a falling out with gnome), or the many many other devs that do have legitimate criticism.

That isn't valid criticism because the whole reason that situation came about is because those devs also wanted to do what they wanted, and it conflicted with what GNOME wanted. No one's at fault here, it's just a normal healthy disagreement. When you start saying "I'm angry, this disagreement means the side I disagree with is shitty bad people, now they owe me" then you're the one pulling the discussion into an unhealthy, toxic territory. So please check yourself and avoid that.

>It can, but if it does then it should expect to lose social capital and good will.

>The good news is that it's a comparatively well connected and well funded open source project

Again, it's really funny that you think any of these open source projects are well-funded or that they ever had social capital to spare. I've seen near constant trolling and bad faith accusations leveled at these volunteers for years, at the same time I've seen nearly all of them struggle with money, and comparatively few people willing to raise a hand to help out. Your problem here is you're not focused on helping rebuild any of this social capital. You're trying to take more of it away and replace it with nothing. It's destructive instead of constructive. I don't know how you can expect anyone to make progress here to rebuild when you're actively taking more of it away with the trash talk.

>on the topic of "finding a common ground to move forward", well that's almost exactly the advice I'd give the Gnome project in regards to rebuilding some of that social capital and good will. But I really do think the ball is in their court at this point, and the claims that they are un-interested in cooperation, or in any supporting the broader open source community, well I'd say that's fair. Most open source software has a certain amount of good will towards other open source software, SDL is a backbone of open source and if they ask you to please reconsider well then... you reconsider. They've helped the broader open source community out a lot so you help them out.

This paragraph is more meaningless fluff. Avoid this. "The GNOME Project" isn't a person that can just decide to do something. It's a loose group of volunteers working on what they want to work on. If an individual (for example, you) wants to go and start cooperating then they just do it. Continuously asking other people to do it for you is an empty gesture. It's time for you to stop thinking like you're a cop or a lawyer throwing accusations around and trying to calculate just how much social capital others have that you can take away from them. Instead think like a diplomat, think how you can help others reconsider and patch things up. Think how you can give back social capital to everyone around you including those you disagree with. Think how you can inspire others to do the same. That's how we make good community members who aren't perpetually starting and continuing these pointless fights with one another. That's how we avoid the toxic obsession with attacking all the small decisions made by some project, and instead we focus on uplifting all projects.

>But with gnome it's very clear that we're not all in this together. Gnome is one team, and the broader open source community is another team. They won't help us out, so why should we help them out.

Please, stop with this nonsense. Again you're viewing this as "GNOME vs SDL" when pitting these projects against one another has never been a reasonable way to approach this. These are just free projects on the internet, they're not in competition for anything. Maybe you think they're in competition for developer time, but they actually aren't. Developer time isn't fungible, you can't take a KDE developer and tell them to work on GNOME, or vice versa. They just won't do that.

>Even the basic appearance of compromise would help this out tremendously, something like "well this doesn't really help Gnome but we'll do it anyway" for a few relevant features. Make it a GSoC project or something.

They do actually do that for GSOC projects, you probably just didn't notice because they didn't do it for the few small areas you apparently care about. With GSOC the intern has to select the project they want to work on, or make a proposal themselves. If no intern ever wanted to work on it then maybe you can understand it was probably a bad idea or not that important or interesting? I should stress that the areas you're talking about are like less than 0.1% of the project as a whole. They might be high priority for you but they aren't for most other people.

>but there is a social contract

No, there isn't. The entirety of these projects could disappear off the internet tomorrow and nobody would do a thing about it. It happens all the time, developers lose interest and open source projects just die. The users might complain but they can't force any developer to do something they don't want to do. If you honestly believe there's a social contract, you would do better to take the first step and start helping everyone, instead of demanding that some volunteer does everything for you.

QUrprUd1nCeicw··on On the Gnome project and “my way or the highway”
There's a difference between honest criticism and low-effort rage bait. Helpful critique is about settling differences and finding a common ground to move forward. It's not about getting mad at others and holding a grudge. Do your best to avoid being that kind of angry internet person with a chip on the shoulder. You also don't owe anyone anything but just remember what goes around comes around. If you spend your time amplifying mistrust and resentment, instead of trying to build and repair trust and appreciation for one another, then you'll always be in a miserable place where you can't trust anybody.

And let me make it clear. I don't care if you honestly criticize GNOME or any other project. I'm pointing out that this style of angry, substance-free criticism is less than useless, it's actually damaging to you and everyone around you because it's the classic short-sighted us-vs-them mentality. It purposely discards the truth in favor of always looking for an "enemy" to blame for everything. Open source isn't a zero-sum game, acting that way is counterproductive towards getting what you want.

>I'm sure you've seen the infamous "you have to decide if you're a gnome app or an everybody else app", and clearly that developer thought other projects owed them something.

No, that's a bad faith misinterpretation of the statement. GNOME, Ubuntu and XFCE all have different APIs that conflict with each other. Acknowledging this fact isn't a demand that anyone owes anyone anything, it's simply a fact. If developers want to use these APIs they have to pick which ones they're going to use.

← PreviousPage 3 of 4Next →