[crashdancer]

>sabotaging everyone else by removing the Tray or the server decoration

Please avoid this narrative. I personally never liked the tray or server decorations and I don't use them other platforms. If you talk to other happy GNOME users you'll see they feel the same. It works fine for me, there's no "sabotage."

[simion314]

>Please avoid this narrative. I personally never liked the tray or server decorations and I don't use them other platforms. If you talk to other happy GNOME users you'll see they feel the same. It works fine for me, there's no "sabotage."

It is sabotage, most people need to use non GNOME apps, like Slack, Thunderbird that need a Tray.

So the solution is super simple, you do not use non GNOME apps then your brain is not affected by a Tray, you do not use non GNOMe apps then your eyes are not bothered by server side decorations, what GNOME did was to try and force everyone to use the GNOME was and they failled, I no longer follow Linux drama closely so I do not know in how many groups did GNOME users fractured? there were 3-4 new DEs based on GTK.

[crashdancer]

None of those apps need a tray though. Personally I have no problem using chat and email apps with only notifications. Something not being to your liking does not mean it's sabotage.

>what GNOME did was to try and force everyone to use the GNOME

I would be very interested to know if you could give a source for this accusation. Just show me one comment from a GNOME maintainer saying they are trying to "force" everyone and how they planned to do it. If they were going into homes and offices holding people at gunpoint forcing them to install GNOME then I think everyone would have heard about that by now.

[simion314]

>None of those apps need a tray though.

What do you mean?

That each time I get of my deska nd then I go back I should either get a stack of notifications or just check each app to see how many emails or messages I missed?

Sure those apps won't crash if soem evil person makes the Tray stuff go to /dev/null.

The idea is if you listen to the users that restored the Tray,a nd the big distros that also restored it or forked GNOME you would be forced to accept the reality, but GNOME designers pretend the reality is wrong and their fantasy is real, somehow reading a book or watching a video about UX makes those guys experts and a big bunch of the community stupid.

Also , stop pretending you are stupid, we all know the big issue with CSD vs SSD , GNOME refusing to make non GNOME apps work on their desktop, check how many forks GNOME vs KDE community had and use logic to understand the real world and non the fantasy in GNOME blogs.

[rleigh]

No. Why should anyone avoid discussing what happened?

We can all see with our own eyes how much GNOME cares about collaboration and interoperability with others. It's zero. It's been this way for a very, very long time. And that disdain for everyone else has consequences.

I used to develop GTK+ applications. I no longer do. Because it was an absolutely miserable experience, working with a toolkit which repeatedly requires every application developer to down tools and do a lot of busy work rewriting perfectly working code when APIs are changed or deleted. No other GUI toolkit causes so much pain and disruption to their userbase. It's quite clear that there is no regard for the actual needs of real application developers, and people like yourself aren't helping. You can't defend the indefensible.

[crashdancer]

You shouldn't avoid discussing what happened, I'm saying you should avoid making unfounded bad faith accusations.

>We can all see with our own eyes how much GNOME cares about collaboration and interoperability with others. It's zero

I mean, the blog post disproves this entire accusation by listing a bunch of projects they collaborate with. This is what I mean: please be more careful with your words. You're disrespecting yourself and the readers of your comments by making these kind of hyperbolic statements.

>which repeatedly requires every application developer to down tools and do a lot of busy work rewriting perfectly working code when APIs are changed or deleted. No other GUI toolkit causes so much pain and disruption to their userbase

GTK isn't the first or only project to deprecate and remove APIs, Qt does is it in every new version too. And you don't have to do this unless you're upgrading to new versions. Some projects are still using forked versions of old Qt and GTK for these reasons. That's totally something you can do.