Hacker News Reader

Comment by ironmagma | Hacker News Reader

I'm talking more about methodology. There are a lot of "forgot to set the dirty bit" type bugs in GNOME-based applications. UI moved on to declarative rendering ages ago, and GNOME never got the memo. When you are writing Flutter or React it's virtually impossible to make those mistakes.

View on HN

It is not Gnome fault. It is more related to design of GTK API

Gnome can choose the tech. They can also build a reactive layer on top of gtk to eliminate a class of issues. Or adopt Grex https://refi64.dev/posts/introducing-grex.html Or...

If Gnome keeps rewriting apps and making mistakes, that's very much Gnome's fault.

GTK is a core gnome project. It's entirely gnome's fault.

It keeps getting worse with each version, and they drag a big part of the open source community with them, because so many apps depend on GTK. Especially important ones like Firefox and Chromium. It absolutely sucks when Gnome controls such a large chunk of the open-source ecosystem.

In fact, it was Gnome that dragged Debian into the systemd debacle. Lennart Poettering managed to convince the Gnome developers to introduce a hard dependency [1] on systemd.

1. https://news.ycombinator.com/item?id=31993161

100% agree - there is so much similarity between those projects. They will be defended to the hilt but you only start to see the tangled vines when you try to build something without them. If you try to pull them out all other software goes too in a big clump. Then their developers ‘own Linux’.

But then again, it is Gnome's fault to pick the wrong tool for the job.

Who maintains that again? :)

Reply on news.ycombinator.com