It's not the GTK developers who decide this, it's the distribution maintainers. T
Huh?
It was the GTK developers who declared GTK2 unmaintained [...] So the distribution maintainers simply followed what the developers stated. [...]
it seems that you (and many others) are arguing that any piece of software that is considered by its developers to be
feature complete,
fully functional, and
requiring of no further changes is immediately, by definition, 'unmaintained' and should be replaced/removed from distros?!
from what folks seem to be saying, and my own observations of the whole ecosystem, the above is how Desktop Linux works, leaving everything in a continuous state of flux. as one package is replaced with a newer version this in turn triggers a need to replace any upstream or downstream packages; every single package needs to have a team of developers permanently 'attached' to it, perpetually ready to kick off a cycle of renewal when triggered by the renewal of any adjacent package.
what has happened to the concept of stability in the world of Desktop Linux? the notion of things that work, have worked for years gone by, and will continue to work for many years into the future. just like microsoft's win32 API since 1998.
cheers,
rob :-)