Applications written using the original Win32 API are binary and source compatible with the current version of the API. Why does GTK keep breaking backward compatibility?<p>I understand breaking backwards compatibility a first time, maybe out of a failure to plan ahead, but not multiple times.<p>It would be easy enough to add new subroutines to add more functionality. Is there a reason to change or remove old subroutines of which I’m not aware? Otherwise this is just causing extra work for application developers for no good reason and in many cases killing old stable applications which are no longer developed.
From the website:<p>> GTK is the core of the GNOME development platform, but it can also be used to write applications for other Linux environments, as well as applications targeting Microsoft Windows and Apple macOS.<p>I'd love for some hn folks to share feedback on portability and overall value of using GTK for multiple platforms.<p>What other engines/platforms exist? I know of Kotlin for mobile/web but besides Electron, I'll have a hard time picking something for desktop apps, should portability be a requirement...<p>PS: I have a love-hate relationship with Electron. I guess I'm not the only one, so I won't elaborate.
Jetbrains is working on this
<a href="https://www.jetbrains.com/lp/compose/" rel="nofollow">https://www.jetbrains.com/lp/compose/</a>
Did the Cairo-situation[1] which was aired somewhat prior to this release work out somehow?<p>At the time it did look somewhat dire.<p>[1] <a href="https://news.ycombinator.com/item?id=25076197" rel="nofollow">https://news.ycombinator.com/item?id=25076197</a>