3 ms·

I don't really understand the hate either

• Nursie 4y ago
  When Gnome 3 was introduced, they not only changed everything, without any way to get it functioning anything like how people were used to, but they also made it more or less impossible for Gnome 2 and 3 to reside on the same box. Overnight a system upgrade massively broke workflows with no way to go back. Yes, it was the distros that chose to ship it like this, but the gnome folks also announced the Gnome 2 was deprecated and would receive no support, pretty much instantly. This left a sour taste with a lot of folks. It looked like deliberate sabotage of what had been a nice, stable DE. Personally, at that point I switched to Xfce and I've never looked back. Gnome is about the last DE I would investigate if I did want to switch away, purely because of the history.
• squarefoot 4y ago
  I think it could be actually directed to GTK rather than to Gnome itself. Gnome lately assumes everyone uses it on a mobile platform touch screen; fine, there are many desktop environments so I'll use a different one, but when this assumption comes from GTK now Houston we have a problem since a huge number of Linux desktop applications use it. I don't have anything against Gnome and actually sorta liked it on tablets, but the way GTK devs ignore every standard drives me absolutely insane. They made a sudden paradigm shift so that a plethora of desktop apps today compile with a GUI library that wants to be run on mobile. Sorry, that is not the way to go: want to add mobile functionality? Great! I fully support it, but please don't enforce it. What about a flag to be #defined at compile time and used only if the app code completely honors it? I hope somebody will create a patch or something to undo that behavior.