3 ms·
> I would hardly consider the GIMP developers (who became the early developers of GTK) to be rash in their option not to adopt a language that had only been ava
by Dylan16807 4y ago
> I would hardly consider the GIMP developers (who became the early developers of GTK) to be rash in their option not to adopt a language that had only been available for a couple of years in the open source world.
I think you misunderstood the criticism. They didn't say GIMP used the wrong model when it started, they said the greater community was wrong for copying GIMP later on.
> And all these years later, at a time when Apple has essentially abandoned Objective C, GTK and Glib continue to provide bindings for dozens of languages to create cross-platform GUI applications, and even if many of us don't agree with the direction(s) it has taken, GTK itself has continued to evolve, whereas UI libraries that came with Objective C have become frozen in time.
The suggestion is that Objective C should have been used instead of GObject. That doesn't mean having to use any particular libraries. And the same work to bind and evolve could have been poured into any reasonably solid library.
- bonzini 4y agoThey did not copy GIMP, they literally extracted the widget code out of GIMP (and with it the object model) and made it into an independent toolkit. At the time there was no decent free toolkit at all, people were trying to reimplement Motif (Lesstif) or Qt (Harmony) but GIMP's was the first free software toolkit for X11. Then over time it was extended beyond widgets, and the tooling around it grew to focus on exporting introspection information for language bindings.
- PaulDavisThe1st 4y agoMy guess is that you can't point to a single example of a library written in ObjC that has any other language bindings, and if you can, it is barely used by anyone. The GTK community always made the idea of language bindings a central part of their development ethos.