Why does Inti contain yet another C++ binding for GTK+?
Because Inti::Gtk’s technical goals are not compatible with existing bindings. I spent quite a bit of time and effort talking to the gtk– maintainers about merging the projects, but in the end we decided that a merger would involve abandoning the design goals of one project or the other, and neither of us were willing to give up the features we wanted to avoid duplicating a few thousand lines of code. Inti is a genuinely different project from gtk–. However, it is based on a thorough study of gtk–, and the gtk– developers strongly influenced the Inti::Gtk design. One somewhat philosophical difference between Inti and Gtk– is that the Inti::Gtk module presents a smaller API with less programmer flexibility than Gtk–. For example, Inti::Gtk widgets have a single model for memory management (equivalent to objects with manage() called on them in Gtk–); you can’t select at runtime what sort of memory management you want as you can in Gtk–. Inti::Gtk doesn’t try to present an STL con
