This is misleading as Lazarus and Delphi both have features that the other one does not, that doesn't make one "behind" than the other. Lazarus is a community driven project, if someone needs something to be implemented they can implement it themselves - and if something is not implemented then nobody really needed it enough to do it.
Also there is no such a thing as "Gtk migration", since sadly Gtk is not backwards compatible with its own major versions, every new version needs a new LCL backend. But existing backends are not replaced (there is no migration from one to another) and any ongoing work reflect the interests of the people using it. Personally i have contributed to LCL and i dislike Gtk3 and later versions of Gtk so i do not even bother trying Gtk3 or later, but i have contributed several fixes for both Gtk2 and even the Gtk1 backends. Also i have implemented Win32 fixes, including MDI support (which wasn't available for years) since that was something that i wanted.
Also FWIW there are also Qt-based backends. I haven't used them much but some developers prefer to use Qt as a backend instead of Gtk.
> No it is not, as most people care about Delphi support on Lazarus, not the other way around.
The majority of Lazarus users do not care about Delphi at all, they treat Lazarus as a project of its own, not a free version of Delphi. Lazarus (and Free Pascal) developers provide Delphi compatibility where that makes sense to let people convert their Delphi projects to Lazarus and allow component authors to share code between Delphi and Lazarus, but it was never meant to be 100% compatible nor replicate everything Delphi does.
If you want to share code between Delphi and Lazarus/FPC you are expected to restrict yourself to the common set of features between the two - and even then you are still going to have to do convertions between the two (AFAIK the form format is incompatible and you need to use Lazarus to convert Delphi forms to it) and use IFDEFs in the code.
> Likewise, it is misleading not to consider moving to the actual, maintained Gtk version, migration.
There is nothing misleading here nor there is any migration going on, i explained how the widgetsets are developed very clearly. There are some people working on Gtk3 and AFAIK there is even some Gtk4 code but those are not going to replace the existing Gtk1 and Gtk2 widgetsets. In fact Gtk is not even the only toolkit(s) supported as there are also Qt4, Qt5 and Qt6 widgetsets.
> Whatever how one feels about Gtk development process, supporting the actual version is quite relevant for most people.
And these people can easily help develop the version they want to use, which is precisely what i've done myself. Again, it is a community driven project.
