← Back to context

Comment by kgeist

4 years ago

>The biggest problem with GNOME right now is Gtk3 and gtkfilechooserwidget.c. It is so spaghetti and so many things rely on it that no one at GNOME is willing to work on it for fear of breaking something.

I wonder, why can't they introduce something like gtkfilechooserwidget2.c leaving the original widget intact?

The big guest Jon for me is, in 2022, why write UI code in C? (I say this as one who contributed to GNOME a little (all icons) back in like ’98–’02 and who writes high-performance C++ professionally.)

A lot of work, maybe? Also, bug-to-bug compatibility?

  • It could be a cleaned up version of the widget minus the warts. Applications wouldn't need bug-to-bug compatibility if it was a conscious choice to upgrade to a new widget.