Re: First deprecate APIs and then remove them in the next major version
- Date: Wed, 13 Dec 2017 15:08:46 -0800
- From: Christian Hergert <christian@xxxxxxxxxx>
- Subject: Re: First deprecate APIs and then remove them in the next major version
On 12/13/2017 04:05 AM, Sébastien Wilmet wrote:
Can I remind you that most of the biggest GTK+ apps are still using
GTK+ 2? MonoDevelop, GIMP, Ardour, …
MonoDevelop is still Gtk2 because Novell/Xamarin/Unity3d invested, quite
literally, millions of dollars on consultants to work on the OS X port
(without much interest in paying additional money to have that work
upstream'd or ported to Gtk3). Add to that the necessity to write new
bindings around G-I for Gtk♯ 3 and you can get the idea of how they see
that as risk from a business standpoint.
Ardour could never move to Gtk3 because a number of VST plugins use Gtk2
and you cannot mix both into the same process space. DAW authors will
often cite the necessity for plugins to be in process to allow for a
large number of tracks/plugins due to context switching. (This is a
contributing factor to why many DAWs write their own UI toolkits).
As for GIMP, I think the lesson I take away is that we need to recruit
people to go do the ports for important projects rather than expect them
to track us. Red Hat has shown that this strategy works in both Firefox
and LibreOffice (which are arguably the two hardest applications to port).
gtk-devel-list mailing list